Use a "url" property (rather than overloading the "data" property) to pass a URL to "GeoJSONSource"
Open
Nobody has claimed this yet.
breaking change :warning:
feature :green_apple:
- Dominant language
- TypeScript
- Stars
- 12.4k
- Forks
- 2.4k
- PR merge metrics
- No merged PRs in 30d
Description
A GeoJSON sources can accept either an URL or objects via the `data` parameter. Internally, we disambiguate these two cases with `data` and `url` properties. We should make the external interface use separate `data` and `url` properties too.
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 locating GeoJSONSource, the entry point named in the issue, and trace how its public data parameter reaches the internal data/url handling. Done means the external interface accepts separate data and url properties while preserving object and URL inputs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100