Extensibility when navigating inside a "virtual" table
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 35
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
Some implementers have implemented a virtual table; navigation of editableCell depends upon the ability to find the previous/next row or column. It would be nice to bake in a extensibility model here, so implementers can communicate with the bounds checking in editableCell and adjust their current "virtual" posiition before editableCell decides it can't move further.
Contributor guide
No contributing guide indexed for this repository
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 editableCell navigation and bounds-checking path described in the issue. Determine how a virtual-table implementer could communicate updated row or column bounds before movement is rejected; done means an agreed extensibility model for navigation at virtual boundaries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100