This document is subject to change, particularly at any point it is deemed necessary to add or revise something.
- Develop a top-quality IntelliJ language plugin
- Enhance the usability and maintainability of soy files
- Leverage the most powerful features of IntelliJ IDEA to promote a superior developer experience
- I18N support (still looking for translators)
- Automated tests designed to ensure a quality release every time
Well, considering the complexity of parsing Closure templates, and this project does not use the closure compiler to perform parsing, it is entirely likely that I missed something.
First, be sure you are running the latest version of the plugin. I deliberately prioritize fixing parser errors above all other bugs and feature improvements. My coworkers use the plugin daily and I consider myself accountable if they loose productivity on account of the plugin.
If you find that your bug is genuine, please report it at Non_Dairy issue page and I'll get to it as soon as I can.
Please include:
A description of the problem A stack trace (if available) or a screen shot Steps to reproduce the error A sample source file if possible
In short, no. I know that there were a few minor bugs left in IDEA 9 and some nastier ones in 10, but nothing that should crash the IDE. The new work is built on top of architectural changes made for IDEA 11, and back porting recent improvements would consume a tremendous amount of time.
There is a fairly exhaustive list of things I'd like the plugin to do at some point, but I'm one guy with a full-time job and a family. "We get there, when we get there."
The big list is on GitHub. Additional ideas are welcome. Prioritization is tracked on little yellow sticky notes and entirely subject to available time, feasibility, ROI, and public demand.
Simply put, our team started using Closure Templates in our project because they are nifty. As an avid IntelliJ IDEA user in an IntelliJ IDEA shop, I was disappointed there wasn't one already... so I built one.