feat(configuration): Allow app configuration to be validated against a schema - #2590
Merged
Conversation
daffl
force-pushed
the
configuration-validation
branch
from
April 4, 2022 22:33
5a49020 to
463f3a2
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This pull request adds the option for
@feathersjs/configurationto validate the application configuration against a Feathers schema to more easily catch potential configuration errors early. It also adds a schema for the authentication configuration which can be re-used. This plays nicely with the new ability for TypeScript to makeapp.get()typed.