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.
Thursday, 14 February 2019
Monday, 4 June 2018
API components now support v1 web components spec
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.
Tuesday, 13 February 2018
Automate Your Work With Request Actions
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.
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.
Monday, 12 February 2018
RAML landed into Advanced REST Client
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.
Tuesday, 5 December 2017
Using Polymer web components in React application
Today I've released a first version of the node module to wraps Polymer powered web components into React component.
The wc-reactor module takes a web component declaration (source code) and uses Polymer analyzer to get information about the component. Finally it creates a bridge between React and web platform so you can use any Polymer web component in a React application as if it is a React component.
The wc-reactor module takes a web component declaration (source code) and uses Polymer analyzer to get information about the component. Finally it creates a bridge between React and web platform so you can use any Polymer web component in a React application as if it is a React component.
Friday, 10 November 2017
Moving Data From Advanced REST Client Chrome Application To The Native Application
If you are ready to install new Advanced REST Client native application probably you would like to move your data along with you.
Unfortunately there's no automatic way to move the data from Chrome application to new native application. This has o be done manually by exporting the date to file (or to Google Drive) and then import it in the new app.
Let's start with installing Advanced REST Client native application if you haven't done that already.
Install
After new application is installed go to ARC Chrome application and export the data.
Unfortunately there's no automatic way to move the data from Chrome application to new native application. This has o be done manually by exporting the date to file (or to Google Drive) and then import it in the new app.
Let's start with installing Advanced REST Client native application if you haven't done that already.
After new application is installed go to ARC Chrome application and export the data.
Tuesday, 7 November 2017
ARC components in Mulesoft's API Console
I am proud to announce that web components that are used to build ARC are now also used to build Mulesoft's API Console.
MuleSoft's API Console is a full-fledged API documentation tool that generates mobile-friendly web documentation based on RAML (Restful API Modeling Language) documents. It is an open source, community driven application that can be easily adjusted to any environment.
While working on atomizing Advanced REST Client to a set of web components internally in the company we've realized that both products can share the same code base. So over a year ago I've started working on new version of the API console. The task was to create a best in class usability for API documentation tool. That includes mobile friendliness, ergonomic design, ease of reading documentation and learning the API structure. From a developer standpoint API console should be easy to use as a standalone application ready to run on a web server but also as a embeddable HTML element that can be added to existing products (like existing web pages with API documentation).
API console is a web application based on web components standard. Therefore it can be used in any web environment and can work with any web framework (though some frameworks - like React - may require additional customizations). We've created a set of tools to make it even easier to build the API console from a RAML file. Our CLI tool can be used to generate production ready standalone website with API documentation or to generate development preview of the documentation while working on RAML. There also is the api-console-builder npm module that can be used in node environment to build the same API console.
Try new API console and design your APIs with RAML. I'll be happy to hear a feedback from you.
MuleSoft's API Console is a full-fledged API documentation tool that generates mobile-friendly web documentation based on RAML (Restful API Modeling Language) documents. It is an open source, community driven application that can be easily adjusted to any environment.
Background
While working on atomizing Advanced REST Client to a set of web components internally in the company we've realized that both products can share the same code base. So over a year ago I've started working on new version of the API console. The task was to create a best in class usability for API documentation tool. That includes mobile friendliness, ergonomic design, ease of reading documentation and learning the API structure. From a developer standpoint API console should be easy to use as a standalone application ready to run on a web server but also as a embeddable HTML element that can be added to existing products (like existing web pages with API documentation).
The result
API console is a web application based on web components standard. Therefore it can be used in any web environment and can work with any web framework (though some frameworks - like React - may require additional customizations). We've created a set of tools to make it even easier to build the API console from a RAML file. Our CLI tool can be used to generate production ready standalone website with API documentation or to generate development preview of the documentation while working on RAML. There also is the api-console-builder npm module that can be used in node environment to build the same API console.
Try new API console and design your APIs with RAML. I'll be happy to hear a feedback from you.
Subscribe to:
Posts (Atom)