-
Notifications
You must be signed in to change notification settings - Fork 3
Strict mode #126
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
Strict mode #126
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
| }), | ||
| strict: Flags.boolean({ | ||
| description: 'Run in strict mode, this will block non-web actions from being run directly', | ||
| defaullt: false |
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.
typo default
| } | ||
|
|
||
| if (invoker && !sequence) { | ||
| if (invoker && !sequence && !actionConfig.strictMode) { |
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.
Where is the serveNonWebAction code? That needs to be resurrected here (it was deleted in the previous PR) and enabled by --strict. If not the e2e tests will fail since they expect 401s for non-web actions being called.
|
stale |
Description
We shortcut some logic to make it quick and easy for developers to test/debug their non-web actions. This pr adds a --strict flag to closer mimic the behavior of Adobe Runtime.
Related Issue
Motivation and Context
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist: