Centralized place for isSupported checks
- Dominant language
- JavaScript
- Stars
- 15.7k
- Forks
- 3.9k
- Avg merge
- 4d 6h
- Merged PRs (30d)
- 34
Description
`isSupported` checks are all over the place and not always consistent.
* Static functions on the file - `PointCloudShading.isSupported`
* Part of Entity - `Entity.supportsMaterialsforEntitiesOnTerrain`, `Entity.supportsPolylinesOnTerrain`
* Part of a Scene instance - `scene.pickPositionSupported`
Would it be better to have a centralized place for these checks?
Contributor guide
Research direction
Start by comparing the existing isSupported checks named in the issue: PointCloudShading.isSupported, Entity.supportsMaterialsforEntitiesOnTerrain, Entity.supportsPolylinesOnTerrain, and scene.pickPositionSupported. Determine whether a centralized location can cover these different ownership patterns and define what consistent behavior would mean. Done requires an agreed design and corresponding updates across the affected checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100