Converting Node information to Const might be wrong behaviour
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
Review commit ae6764f9a9c8606690af504337be55e2fa347540 and trace how node information reaches editorExtension. Inspect where nodes are converted to const and determine which information becomes inaccessible. Done means the intended behavior is agreed and the editorExtension handoff reflects that decision.
Written by the indexing model from the issue text.
Description
With commit ae6764f9a9c8606690af504337be55e2fa347540, Node information is passed to editorExtension. This is clearly a needed functionality. The issue is, the nodes first converted to "const" before passing. This makes accessing some information hard or impossible. I need to check if this is the behaviour we want.
- Dominant language
- C++
- Stars
- 5
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
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.
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
duckdb/duckdb-wasm#2258 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
objectionary/eo-graphs#75 ·
-
Coarray integration tests carry no LABELS, so run_tests.py silently skips them under every backend Opencoarray
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
FISCO-BCOS/FISCO-BCOS#5642 ·