-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Option to run Svelte without path_builder #21
Comments
Hey @telekid, thanks a lot for raising this, it looks great and I think we'd be happy to make this a configurable option. I'm at the moment a bit busy on paternity leave 😱 but I promise to take a look when I'm back, which should be some time next week. |
Merging PRs from strangers isn’t as important as your new kid? 😂 Congrats - that’s super exciting. When you do have a minute, let me know what you’d like the configuration API to look like so I can open a PR. No rush though, obviously. |
Hi! I think we should add another key in the Can you think of any names? Something on the lines of |
Just wanted to stop by and say I haven't forgotten about this issue. I had to get it on a sprint for work, and it looks like I'll have time allocated sometime in the next four weeks. |
Howdy!
First, just wanted to say thank you for building such a great tool. We're very happy to have found a swagger client that doesn't require us to muck around with codegen.
We're experimenting with a modified version of Svelte that foregoes the creation of the module hierarchy. This allows us further decouple API implementation details (like endpoint paths) from method calls. As an added bonus, it makes method names much shorter. See this PR for more info.
That brings me to my question - would you be interested in accepting a PR that allows Svelte to run without generating the module hierarchy? It wouldn't be much work to modify the above PR to make this a configurable option. We'd love to contribute to Svelte, and it would be great to not need to rely on our own fork if possible.
Let me know what you think. Thanks!
The text was updated successfully, but these errors were encountered: