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

feat(protected_areas): added attributes in database to the API. Fixed broken attributes #30

Merged
merged 2 commits into from
Mar 21, 2022

Conversation

sergiomarrocoli
Copy link
Contributor

Adds some extra fields to the API response, updates the documentation, and fixes some non-working attributes.

To test:

set up this app, making sure db is pointed at your protected planet database
run rake api_users:reset_permissions
make API calls to /v3/protected_areas and /v3/protected_areas/:id
api response should include :green_list_status, :is_oecm, :supplementary_info, :conservation_objectives, :green_list_url, :green_list_status, and :sub_locations should display correctly

@sergiomarrocoli sergiomarrocoli changed the base branch from main to develop March 3, 2022 22:47
@sergiomarrocoli sergiomarrocoli marked this pull request as draft March 3, 2022 22:47
@sergiomarrocoli sergiomarrocoli marked this pull request as ready for review March 15, 2022 17:34
@lucacug
Copy link
Contributor

lucacug commented Mar 21, 2022

This is working well and the code looks good. Just a reminder to run the rake task on staging/prod once deployed to make the changes visible in the response. Happy for this to be merged!

@sergiomarrocoli sergiomarrocoli merged commit bf462e3 into develop Mar 21, 2022
sergiomarrocoli added a commit that referenced this pull request Mar 21, 2022
feat(protected_areas): added attributes in database to the API. Fixed broken attributes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants