forked from geosolutions-it/geonode-mapstore-client
-
Notifications
You must be signed in to change notification settings - Fork 109
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
rest_framework namespace and duplicate URLs #344
Comments
asgharsir
changed the title
Real Cause of rest_framework namespace is not fixed
Real Cause of "rest_framework namespace is not Unique" is not fixed
Jul 19, 2021
asgharsir
added a commit
that referenced
this issue
Jul 19, 2021
asgharsir
changed the title
Real Cause of "rest_framework namespace is not Unique" is not fixed
rest_framework namespace and duplicate URLs
Jul 20, 2021
asgharsir
added a commit
that referenced
this issue
Jul 20, 2021
afabiani
pushed a commit
that referenced
this issue
Jul 21, 2021
afabiani
pushed a commit
that referenced
this issue
Jul 21, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue started with seeing this:
This we see when we use geonode 3.2.x or 3.3.x, but this was not appearing while using the master. I investigated what is different in the master. I found that the issue is related to geonode-mapstore-client, and the genode master is installing the latest/recommended version while, geonode 3.2.x for example, is installing version 3.2.1 of django-geonode-mapstore-client.
But there is no fix in the recommended version also.
mapstore2_adapter
url patterns are part of app config, which is not working for themapstore/rest
. Those URLs are not there in master branch. In 3.2.x there is an additional problem. Themapstore/rest/
urls are all duplicated:Above we can see that all the urls are actually duplicate. This can expose to us, or already exposing to us, to unexpected bugs.
rest_framework.urls
, in the first place? Becausemapstore-client
is supposed to be integrated intogeonode
apps which is already having this. But even if we needed it, a best practice could be to avoid this common name:rest_framework
.namespace is not unique
warning anymore, but we are not havingmapstore/rest/
urls either.Actual Behaviour
?: (urls.W005) URL namespace 'rest_framework' isn't unique. You may not be able to reverse all URLs in this namespace
.mapstore/rest
urls.Expected Behaviour
No violation of unique namespace, specially for our APIs.
No duplicate URLs.
I think the fix is not in not using the namespace, rather it is the realization of the problem. The solution is maybe in fixing the app's configuration module.
The text was updated successfully, but these errors were encountered: