quickwit-oss / quickwit-oss/quickwit
Mapping configuration from example (food for thought)
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 11.7k
- Forks
- 597
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 37
Description
This is more of a vague idea than a really fleshed idea.
I am a huge fan of this extension:
https://marketplace.visualstudio.com/items?itemName=quicktype.quicktype
The idea is at follows...
When creating a model in your favorite language, you paste an example json object and the extension creates the struct (or Class) automatically, with a lot of boilerplate.
You can then tweak it to your preference.
It is a massive timesaver and avoids a lot of typo related friction.
We could use the same idea in the CLI for instance, by allowing the user to copy paste a schema... or even sniff it from the clipboard...
We could also offer a webapp that helps creating the quickwit.json file with a good looking mapping straight from json.
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
The proposal mentions generating a quickwit.json mapping from an example JSON object, through the CLI or a web app, but names no implementation files or tests. First determine which configuration and mapping entry points currently handle quickwit.json, then clarify the scope and acceptance criteria before choosing an implementation path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- cli, developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100