-
Notifications
You must be signed in to change notification settings - Fork 57
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
feat: support 'pattern' in inline edge function config #5749
feat: support 'pattern' in inline edge function config #5749
Conversation
…nction inline config
741278a
to
743405c
Compare
743405c
to
9177c35
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tiny comment on... a comment 😂 but other than that LGTM
@@ -92,25 +100,45 @@ const createDeclarationsFromFunctionConfigs = ( | |||
const declarations: Declaration[] = [] | |||
|
|||
for (const name in functionConfigs) { | |||
const { cache, excludedPath, path, method } = functionConfigs[name] | |||
const functionConfig = functionConfigs[name] | |||
const { cache, method } = functionConfigs[name] | |||
|
|||
// If we have a path specified, create a declaration for each path. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tiny thing but seems like this comment should either move or is outdated?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated in 903e6cc
227d8c9
to
903e6cc
Compare
🎉 Thanks for submitting a pull request! 🎉
Summary
This allows setting
pattern
(andexcludedPattern
) in inline config for edge functions which might result in not needing to use separate manifest json file. Primary motivation is to simplify usage of Frameworks API (but not limited to it as this allows usingpattern
also in user defined function configs as well as good old.netlify/edge-functions
)For us to review and ship your PR efficiently, please perform the following steps:
we can discuss the changes and get feedback from everyone that should be involved. If you`re fixing a typo or
something that`s on fire 🔥 (e.g. incident related), you can skip this step.
your code follows our style guide and passes our tests.
A picture of a cute animal (not mandatory, but encouraged)