Check the correct name when adding permissions object schemas to the schema #2121
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
…schema The `name` property of the schema object is the name of the class (i.e. `Role` for the role object) rather than the schema name (i.e. `__Role`). This happened to work if only the predefined schema objects were used and no user-defined classes had the non-underscore-prefixed names, but broke otherwise.
kneth
approved these changes
Nov 20, 2018
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.
The
nameproperty of the schema object is the name of the class (i.e.Rolefor the role object) rather than the schema name (i.e.__Role). This happened to work if only the predefined schema objects were used and no user-defined classes had the non-underscore-prefixed names, but broke otherwise.Fixes #2120.