-
Notifications
You must be signed in to change notification settings - Fork 1
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
Router extension config #231
Router extension config #231
Conversation
@@ -14,21 +14,26 @@ properties: | |||
required: |
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.
Since this whole struct is part of the submit, and every part is 'nullable', lets have it be both 'nullable' and 'optional'. This is a change we will need to start making across the spec, because it's technically correct. The platform will treat any nullable type as also optional on submit, but will always RETURN null in that space.
Honestly, going forward, marking everything that is nullable as also optional would probably be safest. I can't think of a situation where it's important to have the distinction.
@@ -14,21 +14,26 @@ properties: | |||
required: | |||
- redirect | |||
- forward | |||
- proxy | |||
- caching | |||
properties: | |||
redirect: | |||
nullable: true | |||
type: object | |||
required: |
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.
same comment as above. if they're 'nullable', make them also optional.
proxy: | ||
nullable: true | ||
type: object | ||
required: |
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.
same thing
Add HTTP Caching and HTTP Proxy to the HTTP router extension config