You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First, Thanks for your hard work to introduce the great gem to integrated the inertia.js into rails! 👍
There're a few confused questions about the frontend folder/file naming convention by using it:
What's the best way to naming the frontend folder? snakecase follow Rails way, or other?
What's the best way to naming the frontend file? snakecase follow Rails way, or other?
And there're another question which is met from above points:
could we not to call the render in each controller method(such as #show, #index) expicitly, and inertia-rails can know which frontend file/component should be used through the folder/file/class/method namecast?
If we can, It seems to follow the Rails way perfectly.)
The text was updated successfully, but these errors were encountered:
For now, we don't have a strong convention about that. In my opinion is better to use like Event/Index because is the name of the file in the frontend and they use , in React at least, PascalCase.
First, Thanks for your hard work to introduce the great gem to integrated the inertia.js into rails! 👍
There're a few confused questions about the frontend folder/file naming convention by using it:
And there're another question which is met from above points:
could we not to call the
render
in each controller method(such as#show, #index
) expicitly, and inertia-rails can know which frontend file/component should be used through the folder/file/class/method namecast?If we can, It seems to follow the Rails way perfectly.)
The text was updated successfully, but these errors were encountered: