Skip to content
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

Removed warning messages (Option #2) #113

Merged
merged 1 commit into from
May 9, 2022

Conversation

RReichert
Copy link
Contributor

@RReichert RReichert commented May 7, 2022

Background

This PR is one of two options (see other option #112)

Please read #112 first as it is the preferred option and it outlines the problem.

@sonarcloud
Copy link

sonarcloud bot commented May 7, 2022

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@woodfell
Copy link
Contributor

woodfell commented May 9, 2022

This option is much more in keeping with the spirit of this work originally since it was designed to cater to many different environments and flagging misuse of features was a big deal. That may or may not be the case any more but this one still feels like the "best" option because it only uses options which a package actually exports.

Another way to do this would be to update GenericFindDependency so that all these options default to off when a project is imported as a submodule but still default to on when used as a top level project

@RReichert RReichert merged commit 93df75d into master May 9, 2022
@RReichert RReichert deleted the rodrigor/remove-warning-messages-2 branch May 9, 2022 10:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants