stac-utils / stac-utils/stac-fastapi
Enforce setting id, title and description?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 324
- Forks
- 126
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 10
Description
Not sure whether this is the right place, but out there are tons of APIs that identify themselved in production as "stac-fastapi" in landing page id, title and description, leading to such weird STAC Browser renderings for many different APIs:
Is there a way to enforce setting those values so that people can't just be lazy and all expose such nonsense values for their APIs? That's a big discovery issue that's currently somewhat mitigated by STAC Index, but should probably be solved here...
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how the landing page’s id, title, and description are configured and exposed, then review the issue discussion for an agreed enforcement policy. The STAC Browser rendering and repeated “stac-fastapi” values describe the problem, but the desired validation or failure behavior still needs to be defined before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fastapi, python
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100