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.

Prototype testing - invitation to the usability research

I'm happy to announce that we are ready to conduct a user research on a prototype of new Advanced REST Client.

List of changes is very long. Starting from general UI redesign to change in basic functionality.
The most important changes are:

• new projects will support RAML (RESTful API Modeling Language) standard. Users will be able to import RAML file and use it as a "project". RAML contains API definition with the documentation that will be displayed alongside with the RAML request (new view in the app) and in project documentation page

HTTP client on chrome.socket.tcp

Hi developers,

Many of you asked me about the possibility to setting in a request a HTTP headers that are prohibited in XHR. The spec for this object prevents setting headers like User-Agent, Proxy-*, Accept-Encoding etc. I couldn't do much about it, until now.

I'd like to introduce the socket-fetch library that I've made for Advanced Rest Client. It is an implementation of a HTTP client that is using chrome.sockets.tcp API and create connection directly on socket. This means that the app will no longer have any limitations from transport specification (either Fetch or XHR API). It gives you more control over what you are sending to the server and makes the app even more powerful tool for API testing.