-
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 #4827 - Line layer uploaded to GeoNode is rendered as a point layer #4837
Conversation
Uhm, did you understand what's happening? From the fix you are proposing I notice that basically it is just matter of refreshing the resource from GeoServer? Am I correct? |
@afabiani nope, in this case the reason is that with previous code the gs_layer variable is never set when default style is None, therefore code can't go through the if block where we check jts.geom. |
Codecov Report
@@ Coverage Diff @@
## master #4837 +/- ##
=========================================
Coverage ? 59.54%
=========================================
Files ? 231
Lines ? 12379
Branches ? 1796
=========================================
Hits ? 7371
Misses ? 4400
Partials ? 608 |
1 similar comment
Codecov Report
@@ Coverage Diff @@
## master #4837 +/- ##
=========================================
Coverage ? 59.54%
=========================================
Files ? 231
Lines ? 12379
Branches ? 1796
=========================================
Hits ? 7371
Misses ? 4400
Partials ? 608 |
@capooti your change makes sense, and currently you might have identified a wong test case too
Any chance to fix the test case and make the PR pass? Otherwise I can take care of this. |
@afabiani I can work on this tomorrow |
@afabiani could you explain me why that test is checking if gsconfig is returning a None style for the layer even after the test runs fixup_style on it? |
opening a new one |
This PR fixes #4827 - Line layer uploaded to GeoNode is rendered as a point layer
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.