-
Notifications
You must be signed in to change notification settings - Fork 35
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
Validate configuration properties #569
Comments
DirkMahler
added a commit
that referenced
this issue
Aug 2, 2024
DirkMahler
added a commit
that referenced
this issue
Aug 2, 2024
DirkMahler
added a commit
that referenced
this issue
Aug 2, 2024
DirkMahler
added a commit
that referenced
this issue
Aug 5, 2024
DirkMahler
added a commit
that referenced
this issue
Aug 5, 2024
DirkMahler
added a commit
that referenced
this issue
Aug 7, 2024
DirkMahler
added a commit
that referenced
this issue
Aug 7, 2024
DirkMahler
added a commit
that referenced
this issue
Aug 8, 2024
DirkMahler
added a commit
that referenced
this issue
Aug 8, 2024
DirkMahler
added a commit
that referenced
this issue
Aug 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently it is possible to use config properties files that are not evaluated (because of invalid indent in YAML files...). Therefore it would be helpful if jQA fails while loading the configuration if properties with the prefix
jqassistant
are detected that cannot be mapped to supported properties.The text was updated successfully, but these errors were encountered: