List of potential breaking changes in the next major release
- Dominant language
- JavaScript
- Stars
- 19.4k
- Forks
- 3.1k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 9
Description
Cover issue for breaking changes we should consider for the next major release
- [ ] Remove implicit [per line matching](https://github.com/netlify/netlify-cms/blob/edaf9804eb51c90bfedb666b1747caf33f12b048/packages/netlify-cms-widget-markdown/src/serializers/remarkShortcodes.js#L14) in editor components. See https://github.com/netlify/netlify-cms/pull/5597#discussion_r676183995
- [ ] [Editorial workflow UI for entry deletion](https://github.com/netlify/netlify-cms/issues/5650)
- [ ] Update slate to latest version. See #1347, #441, #5637, #5795 and probably more
- [ ] Remove schema validation for dynamically registered widgets, see https://github.com/netlify/netlify-cms/issues/2138#issuecomment-998726513
- [ ] Upgrade emotion, see https://github.com/netlify/netlify-cms/issues/793#issuecomment-1005143962
Contributor guide
Research direction
Start with the checklist and the referenced remarkShortcodes.js line, then read PR #5597 and issues #5650, #1347, #441, #5637, #5795, #2138, and #793. Done means the release team has resolved or explicitly decided each listed breaking-change candidate, including the Slate and Emotion upgrade references.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- release
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100