-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
fix: schema for the host
option
#3549
Conversation
Codecov Report
@@ Coverage Diff @@
## master #3549 +/- ##
==========================================
+ Coverage 93.53% 94.00% +0.46%
==========================================
Files 18 18
Lines 1284 1284
Branches 431 431
==========================================
+ Hits 1201 1207 +6
+ Misses 77 71 -6
Partials 6 6
Continue to review full report at Codecov.
|
"anyOf": [ | ||
{ | ||
"enum": ["local-ip", "local-ipv4", "local-ipv6"] | ||
}, | ||
{ | ||
"type": "string", | ||
"minLength": 1 | ||
} | ||
] |
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.
schema-utils
should respect parentSchema.link/description
, if we don't have link/description for children.
- options.host should be a non-empty string. | ||
-> Allows to specify a hostname to use. | ||
-> Read more at https://webpack.js.org/configuration/dev-server/#devserverhost" | ||
- options.host should be a non-empty string." | ||
`; |
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.
I see the link is not showing only happening with non-empty
error.
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.
Yep, it should be fixed in schema-utils
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.
I think we can merge it as is and update snapshots after fixing it in schema utils
For Bugs and Features; did you add new tests?
Existing
Motivation / Use-Case
fix schema
Breaking Changes
No
Additional Info
Also update options for CLI