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

Create a default blade when a new application is created #3

Closed
leggetter opened this issue Sep 24, 2013 · 9 comments
Closed

Create a default blade when a new application is created #3

leggetter opened this issue Sep 24, 2013 · 9 comments

Comments

@leggetter
Copy link
Contributor

When I run brjs app-create I'd like a default blade to be created.

I may want to run brjs app-create --no-blade to disable the creation of the default blade.

@stevesouth
Copy link
Contributor

This might be a good idea, but I just wonder what the default blade will be called and whether you will always end up having to delete it before you do any work.

On a related note, creating a blade via the command line currently produces a 'presenter blade'. This is not ideal if you don't want to use presenter as there is a lot of code to remove.

@leggetter
Copy link
Contributor Author

Maybe there's a --blade-template flag which identifies the Blade template to use e.g.

brjs app-create myApp --blade-template presenter

But maybe that's adding too much unnecessary complexity? Food for thought when we get here.

@benqus
Copy link

benqus commented Sep 24, 2013

Why not simply go:

brjs new myApp -t (--template) presenter

?

@leggetter
Copy link
Contributor Author

@benqus Because the template is being applied to the auto-generated Blade, and not the app. I think it's clearer. Make sense?

@benqus
Copy link

benqus commented Sep 25, 2013

@leggetter I reckon you might want to specify Blade creation templates as a default option. I would avoid generating Blades with different templates.

@mikes-c
Copy link

mikes-c commented Sep 25, 2013

I think no blade by default, and if you do want one then you have to specify the template (e.g. presenter),
rather than having to specify if you don't want a blade created, or having to delete the code that is created if you forget.

@leggetter
Copy link
Contributor Author

@mikes-caplin Why would you want to create a BladeRunnerJS app without a Blade? Isn't that more of an edge case, hence the --no-blade option.

@mikes-c
Copy link

mikes-c commented Sep 25, 2013

Fair enough if the main use case is creating more complex single page applications. Then the default should be with a blade created (with the default being the presenter blade). And the no blade option for simpler applications, which is only an occasional use case.

@leggetter
Copy link
Contributor Author

I'm happy to close this and we can consider things further as part of #126

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants