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
I need to figure out what runtime code I want to allow users to import.
Thinking out loud.
The Crank.js documentation website is where I am dog-fooding shovel. But there’s also a lot of code there that would be nice have immediately available, e.g. the router and the code for creating front-end builds.
I need to decide: should I make this tool itself front-end framework agnostic? Firewalling specific Crank concerns is an interesting design choice that I have not considered fully for selfish reasons (I want a no-config experience for Crank).
One downside is that I need another layer to create the perfect create-crank-app experience. Naming more things! But the best train to good abstraction is the local.
I think the hardest part to figure out is the router. I feel like routing is important for whatever this tool actually ends up being, and I don’t really know if I want that part to be framework agnostic. Concretely, how do we associate paths with view components? I also have to figure out how middleware will work. Maybe that is the solution to this dilemma.
The text was updated successfully, but these errors were encountered:
I need to figure out what runtime code I want to allow users to import.
Thinking out loud.
The Crank.js documentation website is where I am dog-fooding shovel. But there’s also a lot of code there that would be nice have immediately available, e.g. the router and the code for creating front-end builds.
I need to decide: should I make this tool itself front-end framework agnostic? Firewalling specific Crank concerns is an interesting design choice that I have not considered fully for selfish reasons (I want a no-config experience for Crank).
One downside is that I need another layer to create the perfect create-crank-app experience. Naming more things! But the best train to good abstraction is the local.
I think the hardest part to figure out is the router. I feel like routing is important for whatever this tool actually ends up being, and I don’t really know if I want that part to be framework agnostic. Concretely, how do we associate paths with view components? I also have to figure out how middleware will work. Maybe that is the solution to this dilemma.
The text was updated successfully, but these errors were encountered: