Update Swagger tag descriptions to match Berkeley API GUI how-to guide #682
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
In this branch, I updated Swagger tag descriptions to be consistent with the latest Berkeley Schema-compatible API GUI how-to guide (here). That was my main objective.
While I was at it, I also disabled a buggy feature, where expanding a table within a tag description would simultaneously collapse the endpoints in that tag section; and vice versa. This was happening because the click event was being propagated up the DOM tree, being received be listeners at every level (i.e. there was no
event.stopPropagation()
happening within the tag description level). Now, the table is always visible.Fixes #646
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration, if it is not simply
make up-test && make test-run
.Configuration Details: none
Definition of Done (DoD) Checklist: