You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When attempting to create an e2e project to test an api built with nx-serverless:offline, it fails with a schema validation error because the watch option is passed by the cypress builder, but it is not part of the schema for serverless:offline and additionalProperties is set to false.
Describe the solution you'd like
To the schema for nx-serverlss:offline, either watch is added as e.g. an enum boolean that is always true or additionalProperties is set to true so that unused arguments are simply ignored rather than causing a hard fail.
Describe alternatives you've considered
The only real alternative would be to run 2 separate processes, starting the api manually, then having a cypress instance configured to not run a builder at all.
Check which provider is affected:
[x] AWS
[] Azure
[] Google Cloud Platform
Check which framework is affected:
[] Angular
[] Nodejs
[x] Serverless
[] Lambda
[] Infrastructure as a code
Additional context
I made this exact change in my node_modules and everything ran as expected.
The text was updated successfully, but these errors were encountered:
tstackhouse
changed the title
[FEAT] Update offline schema to not fail on unised arguments (such as watch)
[FEAT] Update offline schema to not fail on unused arguments (such as watch)
Feb 26, 2021
Is your feature request related to a problem? Please describe.
When attempting to create an e2e project to test an api built with nx-serverless:offline, it fails with a schema validation error because the
watch
option is passed by the cypress builder, but it is not part of the schema for serverless:offline andadditionalProperties
is set tofalse
.Describe the solution you'd like
To the schema for nx-serverlss:offline, either
watch
is added as e.g. an enum boolean that is always true oradditionalProperties
is set to true so that unused arguments are simply ignored rather than causing a hard fail.Describe alternatives you've considered
The only real alternative would be to run 2 separate processes, starting the api manually, then having a cypress instance configured to not run a builder at all.
Check which provider is affected:
[x] AWS
[] Azure
[] Google Cloud Platform
Check which framework is affected:
[] Angular
[] Nodejs
[x] Serverless
[] Lambda
[] Infrastructure as a code
Additional context
I made this exact change in my
node_modules
and everything ran as expected.The text was updated successfully, but these errors were encountered: