Issue #1260 Invalid longname of a attribute in error responses #1302
Conversation
This file contains 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
…gn instead of dot)
|
CLA Assistant Lite bot All contributors have signed the CLA ✍️ |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Hopefully fixed Issue #1260 Invalid longname of a attribute in error responses (eq-sign instead of dot)
I wasn't able to find the exact line that the issue #1260 describes. Might be the source code has changed slightly in develop (the issue was discovered in v1.1.1).
Anyway, I searched for all occurrences of "Entity/Attribute not found" in error responses and found ONE where the incorrect attribute long name (the one prepared for mongo db) and fixed it.