You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The configuration of the scanned packages and custom validators would be easier to maintain and share between the CLI (used for example for Maven) and the servlet setup if it could be provided in a JSON file.
The default file that valdr reads could be a valdr.json file that's in the root of the classpath to make configuration even easier.
What about config options that are not shared between CLI and Servlet (e.g. corsAllowOriginPattern and -o)? Should they also be added to the config file? I guess yes...don't see a real problem with that.
Should the config file replace the existing individual parameters or be offered as an alternative? I'd prefer the first even though it'd be a breaking change.
The configuration of the scanned packages and custom validators would be easier to maintain and share between the CLI (used for example for Maven) and the servlet setup if it could be provided in a JSON file.
The default file that valdr reads could be a valdr.json file that's in the root of the classpath to make configuration even easier.
Example:
The text was updated successfully, but these errors were encountered: