Releases: mulesoft/api-console
v3.0.21
Bug fixing
v3.0.20
Body with files
- New: Support for sending files
- New: Added demo page for adding distributed content into the console.
- New: Added demo page for selecting an API version inside the console.
- New: Added
noAttribution
option. Attribution is now part of the console instead of the builder. - Update: redesign of the "body" editor in the request editor
- Fix: Console is not completing the path whit host and port when Base URI set relative #502
- Fix: Title of the API is not fully displayed #519
- Fix: Add ability to add custom content to the console element as a distributed child #520
- Fix: How to enter application/x-www-form-urlencoded for a post body? #374
- Fix: No feedback for file type #199
- Update: Updated demo pages of the console. See
demo
folder for more information
Now Available: API Console v4.0
I am excited to announce a new version of the API Console. The 4.0 release comes with a completely new and responsive UI, improved capabilities for trying out your API, and additional tools to integrate automated builds into your CI/CD pipeline.
Resolved Issues
- Fixed an issue where the console did not render an example that has additional facets (e.g. displayName) where the instance is defined inside the “value” facet.
- Fixed an issue where some HTTP status codes and its content are not rendered by the console when defined inside a security scheme.
- Fixed an issue where the API console was unable to display JSON schemas that contain patterns that include the pipe character.
- Fixed an issue where boolean inputs are rendered as ‘false’, but they were resolved to ‘true’ when making a request from the TryIt view.
- Optional parameters are not shown in the URL inside the TryIt view anymore.
- All type information from multiple libraries are shown now.
- Array types are rendered correctly now.
- Default values for ‘baseUriParameters’ are shown in the input fields inside the TryIt view now.
- Fixed an issue where the security schemes additional header information disappeared when switching between HTTP verbs.
- Markdown headers are rendered correctly now.
- Fixed an issue where optional parameters where required for making requests.
- Fixed several issues with custom security schemes.
- Fixed an issue with linking to specific resources or HTTP verbs.
Improvements
- New and responsive user interface.
- Change URL inside the TryIt view before sending request.
- Improved support for security schemes like OAuth 2.0 in TryIt view.
- Built on top of Web Components which makes the entire API console very flexible.
- Render dropdown list for enum values in the TryIt view.
- Render examples inside a type listed in the type section.
- Contextual documentation for input fields inside the TryIt view.
- New build tools (e.g. CLI) to make generating the API console much easier.
- Render ‘displayName’ instead of the resource path if present.
Breaking changes
- The API console is using Bower as a package manager. It’s not available on npm anymore. Version 3.x will be available on npm.
v3.0.19
v3.0.18
v3.0.17
Bugs:
The order of query parameters should be preserved
Overflow in the body examples
RAML 1.0 array types not working
Why does the console render the same information twice?
Parameters examples are not shown when defined in a response
Arrays defined using type expression shortcut are not displayed ok
Multiple inheritance types render incomplete in method response
Missing description and examples when using Pass Through security scheme
Validation of uriParameter fails when using custom type
Show examples for types
After closing a root-level method section, it can't be re-expanded
Bumped Parser to v1.1.20