feat(#1496) Allow ignoring path fragments from the collection configuration file #1514
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 resolves #1496 by enhancing the
bruno.json
collection configuration file with a new property namedignore
allowing to specify a list of path fragments which should be excluded when loading a collection.For instance :
Collection creation behavior has also been updated so that default exclusions initially handled in the code (node_modules, .git folders) are now written by default in the collection configuration file.
Opening legacy collections will work as expected as default exclusions will be applied if no exclusion configuration can be found.
The collection info tab has been updated in order to display the list of excluded path items
Contribution Checklist:
Note: Keeping the PR small and focused helps make it easier to review and merge. If you have multiple changes you want to make, please consider submitting them as separate pull requests.
Publishing to New Package Managers
Please see here for more information.