Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Clarify error message when creating an ontology with an invalid name #3476

Merged
merged 10 commits into from
Jan 28, 2025

Conversation

seakayone
Copy link
Contributor

@seakayone seakayone commented Jan 27, 2025

Pull Request Checklist

Task Description/Number

Issue Number: DEV-

PR Type

  • build/chore: maintenance tasks (no production code change)
  • docs: documentation changes (no production code change)
  • feat: represents new features
  • fix: represents bug fixes
  • perf: performance improvements
  • refactor: represents production code refactoring
  • test: adding or refactoring tests (no production code change)
  • deprecated: Deprecation warning (ideally referencing a migration guide)

Basic requirements for bug fixes and features

  • Tests for the changes have been added
  • Docs have been added / updated

Does this PR introduce a breaking change?

  • Yes

@seakayone seakayone force-pushed the feat/clarify-error-message-for-invalid-ontology-name branch from 7a1f0b1 to ab9b8d8 Compare January 27, 2025 14:13
@seakayone seakayone force-pushed the feat/clarify-error-message-for-invalid-ontology-name branch from ab1c750 to f75b0b6 Compare January 27, 2025 16:03
@seakayone seakayone marked this pull request as ready for review January 27, 2025 16:27
@seakayone seakayone self-assigned this Jan 27, 2025
@seakayone seakayone merged commit 7c16110 into main Jan 28, 2025
10 checks passed
@seakayone seakayone deleted the feat/clarify-error-message-for-invalid-ontology-name branch January 28, 2025 09:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants