React geonode viewer #2
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
Support S3 Remote Storage
Added LDAP install and configure steps in Admin workshop
…port for metadata
AttributeError: 'NoneType' object has no attribute 'name' jazzband/django-polymorphic#201
Fixes admin interface for layers
…anting a string for creating the feature store.
dj_database_url formats the port as an integer, whereas gsconfig is w…
…t-and-html-formats Enable .txt and .html formats exports for metadata
addition to previous patch: format port as str
Lock in the version until issue GeoNode#2544 is resolved
gsconfig now utilizes an attribution dictionary and bumped to newest …
Heading "Docker Usage" was not rendered correctly.
README: fix syntax error
…again without having to use Clear (GeoNode#2681)
One approach to the problem described in GeoNode#2646 This patch uses the Django field definition to get the length, so this can be controlled from that one place and won't get out of sync.
This subtle misunderstanding of Python tends to cause confusing bugs.
Suppose you have a definition statement like 'def function(keys=[]): ...'
This def statement is evaluated once, at import time, to create a function
object. It is at this time that '[]' is evaluated, and it is that ONE
list object which is retained as the default value for 'keys'.
Python doesn't store the expression and re-evaluate it every time the
default is needed, it evaluates it once at import time and the resulting
value is passed for every call where that arg is not given.
To explain this with code, the effect is something like this:
default_keys = []
def function(keys=default_keys):
...
When function() is called with a value for keys, no problem will be seen.
Even when it is called with no value for keys, and we default to that list,
you might not see a problem. The problem that tends to happen unpredictably
is that the mutable default value is mutated. Those changes are persistent
and globally visible to any call of the function which uses the default.
Then the default value is non-empty. Or information leaks across calls
that shouldn't be leaking. Or the same dict keeps growing forever.
To avoid this, we can use a sentinel value such as None, and then check
for that value in the body of the function. It is a cheap safeguard against
situations that can be very annoying.
… exists in the category yet
Fix the Resources section on profile detail page to work when no data…
* Fixed dead link [ci skip] * Fixed some doc links [ci skip] * Fixed License header in some po files * Fixed packaging files copyright * Added OSGeo copyright and CC-SA in documentation
Fixed bug breaking Group Activity view
…ng certain filetypes to be packaged, loading.gif was the most noticeable.
Package up all necessary files
…ons. 2696 Part 1 - GNIP - Better management of View and Download permissions. - Fix flake8 formatting issues
GeoNode#2696 Part 1 - GNIP - Better management of View and Download permissions.
- Fix minor typo with brackets
Add a new template for editing/showing new maps and change just the viewer to use the new ol3-react based viewer add all kinds of assets/deps for the ol3-react based viewer ol3-cesium is a little tedious but is needed for 3d globe
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.
No description provided.