opengeospatial / opengeospatial/bblocks-postprocess
Transform type extension mechanism
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1
- Forks
- 6
- Avg merge
- 5d 10h
- Merged PRs (30d)
- 3
Description
Right now, any string value is accepted for a transform type.
A mechanism to define transform types (e.g., from a register) would be desirable to have.
Contributor guide
No contributing guide indexed for this repository
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 reading ogc/bblocks/schemas/transforms.schema.yaml at the transform type definition around line 61. Determine how transform types should be defined from a register and how that definition should affect validation; the work is done when the accepted types follow the agreed mechanism rather than allowing any string.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100