Fix: Error when saving concept names with spaces #1476
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related issue
Closes #1439
Description
There was an issue where saving an existing concept with leading or trailing spaces in the name would cause an error. This happened because the extra spaces prevented the system from correctly checking if the concept already existed.
To fix this, I added a trim() before the validation step. Now, any spaces at the beginning or end of the concept name are removed before checking against existing entries. This ensures that the validation works properly, and if a concept with the same name already exists, it correctly shows the message:
"Same name concept already exists."
Before Update
before.avni.mp4
After Update
after.avni.mp4