luckyframework / luckyframework/lucky
Lucky Params to_nested_h feature
Open
Nobody has claimed this yet.
feature request
- Dominant language
- Crystal
- Stars
- 2.7k
- Forks
- 172
- PR merge metrics
- No merged PRs in 30d
Description
Imagine you have params that come from some javascript request and they look like
{user: {nickname: "TheDude"}}. It would be cool if we had a method to convert that in to
params.to_h #=> {"user" => {"nickname" => "TheDude"}}
params.to_nested_h #=> {"user:nickname" => "TheDude"}
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 locating the Params conversion entry points, especially to_h, and compare their behavior with the proposed to_nested_h example. Done means nested params such as {user: {nickname: "TheDude"}} produce {"user:nickname" => "TheDude"}.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- crystal
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100