Kunal Dabir

This is because of how kotlin-poet generates codes, and it is their recommended approach to include visibility modifiers. More details [here](https://stackoverflow.com/questions/64914615/kotlinpoet-ommitting-redundant-public-modifier-from-generated-types-and-prope)

This is one of the very useful feature, however we need to carefully design it since we need to ideally parse the query to be able to produce syntactically correct...

This is great start. It would be great if you could cover or plan for cases when: - [ ] file has a diff (the happy path) - [ ]...

Can we look at alternative like a No-Op interface just like slf4j. That way dependency can be swapped at build/compile time without having to change code. in no-op impl all...

apologies for the delay in responding. The changes are looking good. For no-op project, we could go with a multi-module approach rather than additional source set. However, I don't necessarily...

While it's not ideal, I think we cannot meaningfully parse all kind of versions out there. I would keep this issue open for more inputs from community. Thanks for reporting...

Will merge this once current pipeline is green, ie. all checks are passing. Currently to work on #74 it's good to run all checks.

how about `toml` ? I don't personally like it a lot however it it supports what you need and very much like `ini` reference: https://github.com/toml-lang/toml

For posterity, if someone wants to install all the components: ```bash curl -q https://www.solid-ui.com/registry/index.json | jq -r '.[].name' | xargs -I {} pnpm dlx shadcn@latest add @solid-ui/{} ```