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
While working on #46522, @polyfractal has discovered that the parsing for _common.json assumes there is only one object to parse, while the new spec format there are two objects.
The parser needs to be updated to adopt the new structure of the JSON spec.
Following, the difference between the old format and the new one.
- "description": "Parameters that are accepted by all API endpoints.",- "documentation": "https://www.elastic.co/guide/en/elasticsearch/reference/current/common-options.html",+ "documentation": {+ "url": "https://www.elastic.co/guide/en/elasticsearch/reference/current/common-options.html",+ "description": "Parameters that are accepted by all API endpoints."+ },
API spec now use an object for the documentation field. _common was not updated yet. This commit updates _common.json and its corresponding parser.
Closeselastic#46744
API spec now use an object for the documentation field. _common was not updated yet. This commit updates _common.json and its corresponding parser.
Closes#46744
Co-Authored-By: Tomas Della Vedova <[email protected]>
API spec now use an object for the documentation field. _common was not updated yet. This commit updates _common.json and its corresponding parser.
Closes#46744
Co-Authored-By: Tomas Della Vedova <[email protected]>
While working on #46522, @polyfractal has discovered that the parsing for
_common.json
assumes there is only one object to parse, while the new spec format there are two objects.The parser needs to be updated to adopt the new structure of the JSON spec.
Following, the difference between the old format and the new one.
cc @Mpdreamz
The text was updated successfully, but these errors were encountered: