fix: respect excludedPattern defined in netlify.toml
#6533
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Skn0tt
changed the title
excludedPattern not working for edge functions when defined in netlify.tomlexcludedPattern for edge functions
Skn0tt
changed the title
excludedPattern for edge functionsexcludedPattern defined in netlify.toml
…pected-when-declared-in-toml-file
|
The test failures seem unrelated to me. |
eduardoboucas
approved these changes
May 2, 2024
|
We are working on the test failures. Will update you when this is resolved. #6542 |
…pected-when-declared-in-toml-file
…pected-when-declared-in-toml-file
…pected-when-declared-in-toml-file
…pected-when-declared-in-toml-file
…pected-when-declared-in-toml-file
…pected-when-declared-in-toml-file
Skn0tt
deleted the
simonknott/com-663-excludepath-not-being-respected-when-declared-in-toml-file
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Title says it all! We were only looking at the per-function setting for this, not at the per-route setting. This PR fixes that.