pubspec_parse: Added support for false_secrets #1951
+2,251
−0
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.
Description:
This PR introduces support for
false_secrets
in thepubspec.yaml
file. Thefalse_secrets
field allows users to specify files that should be ignored when checking for secret leaks before publishing. This helps avoid false positives during the publishing process.The flutter_favorite_pubspecs.json file contains the pubspec configurations for Flutter Favorite packages from pub.dev. Its inclusion in the test suite is intended to expand the test coverage footprint, specifically to catch any potential parsing issues with the Pubspec class.
Changes:
false_secrets
field toPubspec
class inlib/src/pubspec.dart
.lib/src/pubspec.g.dart
to handlefalse_secrets
.false_secrets
field parsing and behavior in both Map and Yaml formats.flutter_favorite_pubspecs.json
andsample_pubspec.yaml
to cover various cases.Checklist: