Advanced REST Client and API console uses this component to render XML data. We want to retire this component as it does not give any advantage over using Prism library (right now this library is being used to render other types).
The component also causes problems when integrating it into other systems because it uses web workers. I have received many requests to remove use of web worker. My response is always: no data parsing in main thread process as it may cause the UI to hang. Prism also uses web workers but at least we will have one thing less to be worry about.
The "response-body-view" and "response-view" components that uses this component will be changed around July 2019. After this date new version will be released without additional support for XML responses other than Prism highlighting.
See this intent to deprecate here and comment if you'd like to take a part in the discussion.
After a few months of preparation I am proud to announce that more than a half of web components that are part of API components ecosystem now support version 1 (stable version) of Web Components specification. In short, this means native support on all browsers without polyfills.
We recently held an internal MuleSoft hackathon and, as a result of that event, I am excited to introduce a new feature in the Advanced REST Client (ARC): Request actions.
Request actions allows users to define a logic that is executed when the response is ready. Currently, users can assign value to a variable or store the variable. However, the variable can be extended to other use cases.
I am excited to announce the new Advanced Rest Client (ARC) support for RAML specifications. RESTful API Modeling Language (RAML) makes it easy to manage the whole API lifecycle - from designing to sharing APIs. With version 12 of the ARC desktop app, you can now open RAML files and display their API documentation using MuleSoft's API console.