Refactor ApplicationBuilder into Ligare.programming
, removing it from Ligare.web
#165
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
ApplicationBuilder
class currently exists inLigare.web
. This works fine for building web applications, but Ligare is meant to be neutral regarding the type of application a developer wants to build, especially CLI apps. Currently, usingApplicationBuilder
means pulling inLigare.web
as a dependency. In order to avoid that, this change refactorsApplicationBuilder
to instead be defined inLigare.programming
, removing it fromLigare.web
. From there,Ligare.web
extends the refactoredApplicationBuilder
into its own builder for web applications.This refactor also required adjustments to the Config system in
Ligare.programming
to allow more neutral handling of application configuration needs.The
CreateFlaskApp
test class has been updated to support the refactors.Some error messages have been updated to be less obtuse.
Important: the previously deprecated
create_app
andApp[T].create_app
methods have been removed. It was not possible to update these methods to support the refactor without muddying other code unnecessarily, so this PR removes them.