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

Allow for underscores in unit names and aliases. #331

Merged
merged 1 commit into from
Nov 2, 2023

Conversation

olbrich
Copy link
Owner

@olbrich olbrich commented Nov 1, 2023

Fixes #330

@olbrich olbrich added the bug label Nov 1, 2023
@olbrich olbrich self-assigned this Nov 1, 2023
@olbrich olbrich linked an issue Nov 1, 2023 that may be closed by this pull request
@smathieu
Copy link

smathieu commented Nov 1, 2023

Confirming that this fixes our issue. Thanks for this.

@olbrich olbrich merged commit ccae37d into master Nov 2, 2023
11 of 12 checks passed
@olbrich olbrich deleted the 330-unit-not-recognized-error-after-400-upgrade branch November 2, 2023 11:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Unit not recognized error after 4.0.0 upgrade
2 participants