Eliminate the syntactic distinction between "paint" and "layout" properties
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 12.4k
- Forks
- 2.4k
- PR merge metrics
- No merged PRs in 30d
Description
_From @lucaswoj on December 23, 2016 14:34_
The differences between "paint", "layout", and "top-level" properties are becoming increasingly nuanced. Without a firm knowledge of our implementation, it can be hard to reason about the behaviour of paint properties vs layout properties, especially in the context of data-driven styling. It is worth considering eliminating the syntactic distinction between "paint" and "layout" properties (as Studio does), instead providing documentation about the behaviour of each property.
_Copied from original issue: mapbox/mapbox-gl-style-spec#635_
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
No files, tests, or entry points are mentioned. First determine the scope and design for removing the syntactic distinction between paint and layout properties, with documentation of each property's behavior as the intended outcome.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100