Over the last two weeks we finished testing the release candidate for 1.0 and we’re happy to announce that today we’ve launched! There is a complete redesign of our website coming later this week to go along with the launch so keep your eyes open for that.
Here are the release notes for 1.0:
Improved performance of context queries. They now process on their own thread
Correct version of Markdown now ships with each Optic build.
Removed requirement for Node & NPM to run Optic
Updated Editor Connection API to support IDEs that monitor the disk for changes
New Optic Markdown version has production support for mapSchemaToObject property.
Properties no longer throws errors with more complex schemas.
Comments between AST Nodes no longer being deleted on code inserts.
Sync triggering from the main menu fails gracefully now if there are no projects loaded into Optic
Excluded paths are no longer parsed by Optic.
Since we launched the Optic Development Grants program 10 days ago we’ve had several developers apply to create Optic plugins for their favorite IDEs.
Aaron Mead built the VSCode plugin and published the first version on the Visual Studio Marketplace. Download Link: https://marketplace.visualstudio.com/items?itemName=useoptic.optic Source Code: https://github.com/opticdev/optic-vscode-plugin
Another developer has applied for the Sublime grant and is beginning work tonight.
Aidan wanted to test out the spec he wrote for grant applicants so he built a plugin for all the JetBrains IDEs (his favorites) this week. Download Link: [Pending JetBrains Approval] Source Code: https://github.com/opticdev/optic-intellij-platform-plugin
With these new additions Optic now supports VSCode, Atom, WebStorm, IntelleJ, PHPStorm and the rest of the JetBrains products. In the next week we anticipate having Sublime finished as well.
We went all in on adding some useful knowledge for the MERN Stack. Now users can generate Mongoose Queries, CRUD routes, and client side networking code using RequestJS. The entire stack has been Sync enabled so when you make manual changes to your models or API, Optic will propagate those changes across your project.
You can check out an example of Optic being used with the MERN stack here in our new To Do Demo App: https://github.com/opticdev/optic-demo-project
If you want to try it out in your own project, be sure to add these knowledge packages to your optic.yml file: