-
-
Notifications
You must be signed in to change notification settings - Fork 7
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
Trailing spaces #156
Comments
Hum, I didn't fix the issue, I though it was on keys, while it was on values ! |
@aleene shall I trim also spaces at the beginning ? |
alexgarel
added a commit
that referenced
this issue
Mar 5, 2024
fixes: #156 migration was manually tested over a production database import
Sounds good |
alexgarel
added a commit
that referenced
this issue
Mar 7, 2024
fixes: #156 migration was manually tested over a production database import
It's live @aleene :-) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What
When adding a values the system takes into account any trailing spaces. This results in multiple values (one with space and one without), where they should be the same
Steps to reproduce the behavior:
Add a key like
producer_data_issue
and typeEnergy value in kcal does not match value in kJ
. Two suggestions will be shown, one with and one without a trailing space.Expected behaviour
Remove any trailing space before storage.
The text was updated successfully, but these errors were encountered: