-
Notifications
You must be signed in to change notification settings - Fork 242
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
Update to latest master from upstream. #1741
Conversation
@wivwiv is this enough ? or are there extra steps? |
|
With the help of chatgpt, I used this code to check the api title. You can also use it to check import json
import os
swEN = open('./swagger.json').read()
swEN = json.loads(swEN)
for item in swEN['paths'].items():
key, value = item
for item2 in value.items():
method, api = item2
title = api.get('summary') or api.get('description')
if '<br/>' in title:
print({
'method': method,
'key': key,
'title': title
}) |
Oh, yes, this needs another PR merged first. I'll turn this one to Draft and come back with an update.
If this is the desired default procedure now, we should probably update |
2eb1e73
to
82f104b
Compare
Took a bit longer than expected. @wivwiv could you have another look please? I used your script from above to double check and it looked good. Also question remains, should we update the README? |
9577df9
to
d24f6de
Compare
Now with changes from https://emqx.atlassian.net/browse/EMQX-8507 |
This is the workflow for REST API document updates. Sorry for not replying to you earlier. The e5.0.2 has been updated, you can try this process in v5.0.22. Notice: It should be updated only after each release to avoid the API being added to the documentation but not available in the product. |
d24f6de
to
453c020
Compare
PR updated. Created a ticket to include CE/EE and exact version info: https://emqx.atlassian.net/browse/EMQX-9569 |
@sstrigler FYI @LenaLenaPan why this PR has been closed without merge? |
Also contains changes from emqx/emqx#10195