fix: bring summaries in line with STAC spec#282
Draft
ividito wants to merge 1 commit into
Draft
Conversation
ividito
requested review from
aliziel,
anayeaye,
botanical,
sandrahoang686 and
smohiudd
Collaborator
|
@ividito I need to review some development notes but I think this might have been a fast solution to preventing users from editing summaries at all because it could potentially break dashboards that currently rely on a dashboard-specific datetime field in the collection summary. It may be that we just reject summaries updates in a more informative way? |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The STAC collections spec supports, for summaries, set of all distinct values in an array. We previously required these to be strings, but that doesn't work for some collections which are otherwise valid STAC.
I'm proposing a loosened schema for the raw-collection input. I also adjusted the form to show stringified nested values, instead of [object Object], where applicable.