We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
in some cases an admin can choose a name that results in invalid java identifiers, e.g. SHELF-READY.
would it make sense to impose limitations on the octane back-end during creation of names?
temporary fix in PR #143
The text was updated successfully, but these errors were encountered:
another change was required. this is provided in PR #161. this is PR is deemed to be more correct than replacing specific characters.
Sorry, something went wrong.
No branches or pull requests
in some cases an admin can choose a name that results in invalid java identifiers, e.g. SHELF-READY.
would it make sense to impose limitations on the octane back-end during creation of names?
temporary fix in PR #143
The text was updated successfully, but these errors were encountered: