Skip to content

Update template #28, #33, #34#36

Open
m-mohr wants to merge 1 commit into
mainfrom
update
Open

Update template #28, #33, #34#36
m-mohr wants to merge 1 commit into
mainfrom
update

Conversation

@m-mohr

@m-mohr m-mohr commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

Updated the template repository:

  1. Updated dependencies
  2. Updated examples to STAC 1.1.0
  3. Default version is 0.1.0 instead of 1.0.0
  4. Added bands as a field scope Extensions should indicate if they are usable in Bands #34
  5. Added link and asset templates as options
  6. Don't error when we use GitHub note/warning/... blocks
  7. Extensive update of the default schema:
    1. Simplifications for the schema where possible and some more comments (we got more functionality with the same schema length)
    2. Add default schemas for bands, catalogs, summaries, links, asset templates and link templates,
    3. Try to enable some basic validation of summaries
    4. Don't check anymore whether any field of the extension exists in the document. This has proven to not work reliably and makes the schema more complex than it needs to be without providing much benefit.
    5. No template for "required fields" as most extensions don't require fields in specific places anyway and it makes the schema more complex than needed. Individual requirements can still be added by users if strictly needed.

This comment was marked as resolved.

This comment was marked as resolved.

This comment was marked as resolved.

@m-mohr
m-mohr force-pushed the update branch 2 times, most recently from 00c55db to c76962a Compare July 13, 2026 14:31

@emmanuelmathot emmanuelmathot left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Wow. that was needed! Thanks for that!

@gadomski gadomski left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Worth adding dependabot to keep the Github Actions and Node dependency versions up-to-date?

@m-mohr

m-mohr commented Jul 14, 2026

Copy link
Copy Markdown
Contributor Author

Not sure, then I'd get like 50+ PR notifications for the extensions I maintain whenever a dependency update comes in. As we only use the dependencies for "development", I'd say we may better update manually on demand.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

4 participants