Open cpojer opened 6 years ago
This isn't straightforward as I use special css markers to allow my autoindentJSX to work. This causes <
, >
and />
to be logically separated. I'm pretty sure that <>
isn't working using FiraCode either as these are two distinct spans in the css. In short, to support this change I would need to amend the autoindentjsx code quite a bit.
This would be a really cool feature to have! Is there any way that <>
and </>
could be tokenised without messing up the autoindentjsx code? I'm happy to take a look depending on complexity.
React Fragments have a special JSX syntax. I'm using FiraCode and noticed that in Atom, the ligature for
<>
is applied but for</>
it is not. Could this be fixed? I'm happy to help make a fix if you point me to the place and how to test it.The ligature for
</>
is listed here: https://github.com/tonsky/FiraCodeSee
Thanks!