Closed mysy00 closed 4 months ago
Doesn't sampctl create it inside current folder your terminal has been navigated to?
I've just checked, it actually does. Maybe I had been using a modified version in the past that creates it all in a subdirectory for this very reason. I remember playing with its source code but it's been a while. All other tools popular tools that I checked create everything in a subdirectory.
I've just checked, it actually does. Maybe I had been using a modified version in the past that creates it all in a subdirectory for this very reason. I remember playing with its source code but it's been a while. All other tools popular tools that I checked create everything in a subdirectory.
Do you think we should allow users to choose? We could implement something like:
with optional option `pulse init --dir='C:/.../'
or even with optional argument
pulse init Folder
(leaving with no argument specified initializes in current folder)
I think it would be best to do what all other popular tools in the industry do to avoid confusion. Judging by the amount of users, tools like react, next and svelte are the ones settings the standards here.
Later tonight I will try to correct some sentences in a separate PR to make the process of initializing a project clearer to the user.
Later tonight I will try to correct some sentences in a separate PR to make the process of initializing a project clearer to the user.
Affirmative
Thanks!
To mimic behavior of other similar project bootstrappers (sampctl, react, vue, etc.), all projects should be created in a new folder - not the current one.
References: https://vuejs.org/guide/quick-start.html https://nextjs.org/docs/pages/api-reference/create-next-app https://svelte.dev/docs/introduction https://astro.build/