Declarative mutation configs seems to be broken
- Dominant language
- Rust
- Stars
- 19k
- Forks
- 1.9k
- PR merge metrics
- No merged PRs in 30d
Description
So, the idea is great. But the implementation seems to be broken.
This is not true. RANGE_ADD is not an optimistic (It does not work), and NODE_DELETE does not work at all.
There should be a warning in docs that configs does not work reliably, and a manual imperative code is preferred for now.
Contributor guide
Research direction
Locate the documentation for declarative mutation configs and review the claims about RANGE_ADD and NODE_DELETE. Update that documentation with the reported reliability warning and the stated preference for manual imperative code, ensuring the wording matches the current behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100