-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
json spec: allow null for documentation url #55749
Changes from 1 commit
25dcd29
0b37977
dddf74b
f3e5af7
ccbf2dc
3ca7d6f
0e606db
5e47c78
e3d7004
93dfadf
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -119,6 +119,4 @@ validateRestSpec { | |
ignore 'autoscaling.delete_autoscaling_policy.json' | ||
ignore 'autoscaling.get_autoscaling_policy.json' | ||
ignore 'autoscaling.put_autoscaling_policy.json' | ||
ignore 'ml.validate.json' | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think these are stable APIs, so would clash with the previous comment about allowing https://www.elastic.co/guide/en/machine-learning/current/ml-jobs.html |
||
ignore 'ml.validate_detector.json' | ||
} |
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.
Can the use of
null
be constrained only to APIs that have stabilitybeta
orexperimental
? This would align with APIs that are under development, whilst still providing benefit of having links for stable APIsThere 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 made the null conditional. So that only
stable
requires a string, the others (beta
,experimental
, andprivate
) now allow null. 0b37977As you pointed out below, this does indeed cause a validation error on the two
ml
specs below we will need to sort out first.