-
Notifications
You must be signed in to change notification settings - Fork 0
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
Allows metadata upload to dataset having different UUID #1
Conversation
@dorohahn please do NOT branch from the main development line, but from a common ancestor of our main development line and the upstream. This should be Also, make sure to clean up your code (remove duplicates, unnecessary imports, etc.) -- you should take care your code aligns with PEP-8. Also to make sure response codes do match. Changing reponse semantics should be made consistently. In this case I mean especially the lines here: geonode/geonode/layers/views.py Lines 189 to 193 in aced1fa
|
…ID than the dataset
aced1fa
to
ad097ca
Compare
@@ -568,6 +576,7 @@ define(function (require, exports) { | |||
callback(array); | |||
} else if (resp.success === true) { | |||
self.polling = false; | |||
console.log(resp) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should be removed for the feature branch
Update needed: API endpoint |
…tionality of the UI forms to the REST API endpoint i.e., the metadata still gets uploaded when the UUID is different. Adjusted the unit tests for both UI and REST API.
@ahmdthr could you please resolve the issues? |
@dorohahn create a PR against our main development line (
thuenen_4.x
in case of the GeoNode fork) as I do here:Please also link to the actual issue:
Resolves: https://github.com/Thuenen-GeoNode-Development/Sprints/issues/7