deprecate style.load, etc to simplify + clarify eventing
Open
Nobody has claimed this yet.
refactoring :building_construction:
- Dominant language
- TypeScript
- Stars
- 12.4k
- Forks
- 2.4k
- PR merge metrics
- No merged PRs in 30d
Description
per chat w @lucaswoj yesterday and with added motivation from #3958, we should simply eventing by removing all events that do not fall within the schema of the `data` events from #3590, and extending the current implementation to cover the use cases of the old events.
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 reading the data-event schema in #3590 and the related motivation in #3958, then inspect the current eventing implementation and the old events named by this issue. Done means non-data events are deprecated or removed and the old use cases are covered by the data-event implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100