-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[Fixes #11447, #11668] Various fixes in GeoFence permissions #11669
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
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #11669 +/- ##
==========================================
+ Coverage 62.90% 62.95% +0.04%
==========================================
Files 875 875
Lines 52543 52548 +5
Branches 6604 6605 +1
==========================================
+ Hits 33054 33079 +25
+ Misses 17966 17946 -20
Partials 1523 1523 |
giohappy
approved these changes
Nov 9, 2023
giohappy
pushed a commit
that referenced
this pull request
Nov 9, 2023
…#11677) * [Fixes #11447] Bad role name in creating GeoFence rules * [Fixes #11668] Bad ordering of GeoFence rules --------- Co-authored-by: Giovanni Allegri <[email protected]> (cherry picked from commit e7b53a5) Co-authored-by: Emanuele Tajariol <[email protected]>
davekennewell
pushed a commit
to Hydrata/geonode
that referenced
this pull request
Nov 30, 2023
…sions (GeoNode#11669) * [Fixes GeoNode#11447] Bad role name in creating GeoFence rules * [Fixes GeoNode#11668] Bad ordering of GeoFence rules --------- Co-authored-by: Giovanni Allegri <[email protected]> (cherry picked from commit e7b53a5)
chumano
pushed a commit
to cec-tris/geonode
that referenced
this pull request
Dec 24, 2023
…sions (GeoNode#11669) (GeoNode#11677) * [Fixes GeoNode#11447] Bad role name in creating GeoFence rules * [Fixes GeoNode#11668] Bad ordering of GeoFence rules --------- Co-authored-by: Giovanni Allegri <[email protected]> (cherry picked from commit e7b53a5) Co-authored-by: Emanuele Tajariol <[email protected]>
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.
Please merge with rebase.
Checklist
For all pull requests:
The following are required only for core and extension modules (they are welcomed, but not required, for contrib modules):
Submitting the PR does not require you to check all items, but by the time it gets merged, they should be either satisfied or inapplicable.