Skip to content
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

Copy over code from bikeshaving/crank/website? #3

Open
brainkim opened this issue Mar 25, 2023 · 0 comments
Open

Copy over code from bikeshaving/crank/website? #3

brainkim opened this issue Mar 25, 2023 · 0 comments

Comments

@brainkim
Copy link
Member

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.

This was referenced Apr 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant