ManageIQ / ManageIQ/binary_struct
Deprecate definition format in favor of Hash or associative Arrays
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 5
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
Extracted from #7 ...
Note that for the next major version we may want to deprecate the "backwards" format. We still need associative Arrays for if you want multiple nil keys, but I think just supporting Hash and associative Arrays makes the code much simpler. The current definition format feels "backwards"
Contributor guide
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 definition-format discussion extracted from issue #7 and trace where the current backwards format, Hash, and associative Array inputs are handled. Done means the backwards format's deprecation path is defined while Hash and associative Array support, including multiple nil keys, remains available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100