obtain node resource by model name #70
Merged
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
fmigneault
added a commit
to Ouranosinc/Magpie
that referenced
this pull request
Mar 27, 2021
…rat_foundations#70 to remove patch) + fix missing permissions field
|
Thank you! |
|
@ergo Will it be possible to have |
|
@fmigneault I've made a new release for you along with some other changes. |
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.
Because the
ResourceTreeServicePostgreSQLcan receive a custom model (as long as it implements same fields structure asResource), it is possible to reuse this tree and all its useful methods for other similar tables.I employ this in my repo to sync
Resource(local) againstRemoteResourcethat derives fromResource.This fix retrieves the field by name of the model class instead of hardcoded auto0generated attribute named like default
Resourcemodel.