'at' lookup expression requires 'format' to recognize array
Open
Nobody has claimed this yet.
bug :lady_beetle:
- Dominant language
- TypeScript
- Stars
- 12.4k
- Forks
- 2.4k
- PR merge metrics
- No merged PRs in 30d
Description
mapbox-gl-js version: 2.4.1
browser: Chrome
Steps to Trigger Behavior
- create an "at" lookup expression to find a value in an array like:
'text-field': ["at", 0, ["literal", alphabet]], - check for error:
Error: layers.points.layout.text-field[2]: Expected array<formatted> but found array<string, 3> instead.
Link to Demonstration
https://jsbin.com/nomivevati/edit?html,output
Expected Behavior
The expression should find the value in the array if the "literal" type is used.
Actual Behavior
Receive error:
Error: layers.points.layout.text-field[2]: Expected array<formatted> but found array<string, 3> instead.
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 running the linked jsbin reproduction with mapbox-gl-js 2.4.1 and inspect how the "at" expression validates the literal array used by the text-field. Done means the expression accepts the literal array and returns the selected value without the reported array error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, typescript
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100