-
Notifications
You must be signed in to change notification settings - Fork 29
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
Directory based router #45
Comments
I agree with this idea. |
Hi @akku1139 ! Thanks for your proposal. I'm not 100% sure I understand the directory routing for SvelteKit and Next.js App Router, but what is the difference between using
Of course, it would be interesting to be able to separate files for each request, such as GET and POST. In that case, I think it would be nice to have a rule for file names such as |
Personally, I think that pros of directory-based-router equals pros of I don't mind using |
If you use If it can create rules in the package, the problem will be solved, If you decide on a fixed root file in HonoX, it will be the same for all projects, so it is easy to understand, |
I agree with the pros/cons discussed so far. On a personal note, I like the current filename rules because they are as clear as the Controller in Ruby on Rails. Here are some suggestions for a related, but slightly different, client-side component (islands) Currently, even page-specific client-side components must be placed in For example, consider a simple chat application,
I would like to place the client component
However, we feel that it would be better to manage global common components used on each page in For your reference |
I think it is a good idea. However, there is the problem of what to do if you want to create a page called I think it is a good idea to prefix it with some special character to prevent it from being included in the routing. For example,
|
+1
+1 I think both ideas are great. This means that...
These would be simple to implement and easy for users to understand. |
Hey! I've made PR #140, enabling putting an island component, not only in the |
Hi you all. I've released v0.1.12. This release includes the new feature which enables placing islands on the same directory of pages instead of
This enables directory-based routing. Please try it. |
What is the feature you are proposing?
I would like to do directory-based routing like SvelteKit and Next.js App Router.
Either in a way like
(+)page.ts
or separate files for each HTTP method and route them like+get.ts
and+post.ts
.The text was updated successfully, but these errors were encountered: