Skip to content
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

Save default view parameters #179

Merged
merged 12 commits into from
Apr 13, 2018
Merged

Save default view parameters #179

merged 12 commits into from
Apr 13, 2018

Conversation

brew
Copy link
Contributor

@brew brew commented Apr 12, 2018

This PR allows dataset owners to set up and save a default view for their packages. It uses a new /package/update_params os-conductor endpoint to save current view parameters to the package model (openspending/os-conductor#31).

screen shot 2018-04-12 at 10 54 09

Best to review both this and the related os-conductor PR together. These changes are currently live on the staging server: https://staging.openspending.org/.

Closes of openspending/openspending#1187

brew added 9 commits April 5, 2018 17:07
Only use defaultParams if there are no visualizations defined. This
allows users to setup their own params and share the resultant url.
Adds controls for dataset owner to save current view as default. Add
user controls to reset the entire view, or reset the view to the default
parameters.

- Adds a `param-controls` directive to manage the UI and controller code
for the default params.
- View params are saved via the data-package-api to the package model in
the ElasticSearch instance. This is mediated by os-conductor by the new
`/package/update_params` endpoint.
- `confirmation-popover` directive added to UI for the 'Save View As
Default' action, which is only shown to the dataset owner.
Copy link
Contributor

@vitorbaptista vitorbaptista left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I haven't ran it locally, but tried on staging and it's working great 👍 I would just add a few tests, and change Save View As Default to Save View as Default. Pretty good when the only suggestion in a review is to lowercase a word, huh? 😄

Because Elasticsearch update merges object values with existing values,
we need a way to replace the params entirely. We don't have access to
Elasticsearch scripting, so the easiest way is to dump the params object
to a string, and send it as a value of a 'params' key. The stringified
json object is parsed back to an object before use.
@brew brew merged commit e930cf5 into master Apr 13, 2018
@brew brew removed the in progress label Apr 13, 2018
@brew brew deleted the 1187/default-vis-params branch February 8, 2019 08:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants