Allow disabling default build if multiple entry points are defined

[emodric]

Fixes #32.

[weaverryan]

Hey @emodric!

Sorry for the slow attention on this. I merged another PR and created conflicts with this one - could you check those?

I'm +1 for this PR. However, I'm interested in what the error is if you disable the default entrypoint, and then accidentally use a feature without specifying which build you want - I think the user will see errors like "The build _default does not exist" - which isn't a great error.

[weaverryan]

#45 will also help and affect this PR

[emodric]

@weaverryan Will get back to you next week, can't get to it any sooner.

[emodric]

@weaverryan I've pushed the rebased commit. As for #45, how will it help and affect this PR?

When someone uses a default build which has been disabled, the error message is: Given entry point "_default" is not configured.

Maybe we could try to determine which builds are configured and offer them as an alternative in the error message, e.g: The default build is not enabled. Use one of "frontend", "backend", "app1", "app2" builds.

[jRexhmati]

Hello @emodric do you plan to merge this pr anytime soon?

[emodric]

You should probably be asking @weaverryan that :)

[jRexhmati]

@emodric Thanks for the info :)
@weaverryan Do you plan to merge this soon? I can give you a hand ✋if you need

[weaverryan]

Sorry about the slow merge on this - it's a really great PR. Even the README got updated! Thank you Edi!

[emodric]

@weaverryan Thanks for the merge :)

However, what about this part, that you were initially concerned about?

Maybe we could try to determine which builds are configured and offer them as an alternative in the error message, e.g: The default build is not enabled. Use one of "frontend", "backend", "app1", "app2" builds.