meta field from options need to be parsed/processed
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
creating tickets to track it.
Also, enumerating all these requirements helps in reaching better signatures for parsing the input query utility functions.
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
The issue does not name any files, tests, or entry points. Start by locating the input query utility functions and the option parsing path, then determine how the meta field should be parsed and processed; done means the requirement is implemented and covered by appropriate tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend-api-design, search
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100