I mentioned in the previous post that I would create a plugin for less which converted from LTR to RTL. Here is a tutorial post on creating that plugin.
Setting the project up
I know we want to modify the AST (abstract syntax tree), so we will need a visitor plugin - I wrote an example visitor plugin and that would help us in getting started.
We need a
package.json which has a dev-dependency on less but nothing else - this is because less plugins get required from within the less compiler, not the other way round.
The first thing to sort out is tests - because there is no UI, it is crucial we know what is going on. I’ve created a test folder and that can re-use the acceptance tests framework from less. There we have a set of less files and corresponding CSS files. The CSS is generated from the less and then compared to the checked in CSS, which then passes if they are the same. The source is simple..
and we are passing our own plugin in the plugins array so it is used when creating the less. I’ve added two files
Next we need the base of the plugin. Less expects an object with an install function, so in
lib/index.js we have that:
less gives the plugin itself and the plugin manager for this current compile, so it is just a matter of adding a visitor.
A visitor is a class that has a function for each type of node in the AST and then is called on those. So you may have a visitRule function which gets called once for each rule and a visitURL that gets called once per URL node. Here is a basic visitor that doesn’t do anything.
It uses the less visitor base class in order to get the visitor functionality. We can now run the tests in order to check no exceptions occur.
$ node test
LESS - RTL
- test\less\rtl\test: OK
You can see the full commit here.
My next step would be to define simple tests - this means we can verify the tests fail and also debug our solution. Adding
float: left and the reverse in the css and re-running the tests shows..
$ node test
LESS - RTL
- test\less\rtl\test: FAIL
So, going back to the visitor, we want to catch the keyword left when the rule is float. Referring back to the nodes we can write the following.
So, the out appended function is called once all child nodes have been visited. So we store a flag that we are reversing, then if that is set when we visit a keyword, we flip it. However this doesn’t quite work - less uses an anonymous node when it can as a performance improvement, so we need to catch that too. A bit of abstraction later and the test passes. I also add a test that has the reverse and uses a comment, which forces less into using the keyword node rather than the anonymous one. See the commit here.
Reversing Property Names
The next job is to reverse properties like
margin-right. For this we just need to transform the rule node and replace the name with the correct one. We always create a new node as some nodes may be shared and we wouldn’t want to replace a node twice.
Unfortunately at the moment there is no way to clone a node and change just what you need, but it is something I will need to add in the future. See the full commit here.
Reversing Shorthand Properties
Next, we want to reverse shorthand properties. So for instance this is all the shorthands for margin.
We need only replace the last example, swapping the left and right. We can do this by setting a flag and reversing the order when we reach an expression (in less, an expression is space separated, a value is comma separated).
You can see these changes here.
Adding a variable
Lastly, you will come across situations where you do not just want to reverse, but have a conditional. For these situations we will use a pre-process plugin. This allows us to add variables to a file that is compiling. So, back in our index file we add the variable plugin..
and then we implement our plugin…
We update the contentsIgnoredChars in order that the sourcemap offset is correctly updated. You can see this commit here. Finally, since we have a variable we probably want to run the plugin whether we are producing LTR or RTL, so finally we add some options and update the readme.
I have no doubt there are CSS rules I have missed, but I hope this takes some of the mystery out of less and creates something that with a little bit of polishing and bug-fixing can be a useful plugin.
There is also a change we need to make soon which makes extensions like this easier. At the moment comment nodes are added as nodes to the AST, which means that the code that reverses shorthands might not always work if there is a comment in the middle of the value. We need to move comments and white-space inside the nodes and then create a better mechanism for cloning so that plugins can be forward compatible. Its also clear there is boiler plate code in this plugin that could be taken back into the less project, when someone has time.