Encapsulate 3 maps for execution modes in functionItem and DynamicContext
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 246
- Forks
- 85
- Avg merge
- 6d 1h
- Merged PRs (30d)
- 22
Description
Could we encapsulate these three maps in a reusable class, that both function items and dynamic contexts can use? That may simplify the APIs.
Originally posted by @ghislainfourny in https://github.com/RumbleDB/rumble/pull/438
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 locating functionItem and DynamicContext, then review the three execution-mode maps and the context from PR 438. Done means both components use a reusable class for these maps and their APIs are simplified without changing execution-mode behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100