tonsky / tonsky/FiraCode

Ligature request <% <%= %> ERB templates in RoR

Open
#741 0 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

suggestion
Dominant language
Clojure
Stars
82k
Forks
3.2k
PR merge metrics
No merged PRs in 30d

Description

I use ERB templates for Ruby on Rails at work. It works by using the following tags to dynamically add information: <%= foo %> <% bar %> I was wondering if I could request these (i.e <%, <%=, %>) as additional ligatures to Fira Code?

I would imagine that the would look similar to the glyphs with the percent circle on the caret side merged with the caret (similar to the <$ and $> glyphs).

As for conflicts, I have started to do some research into this and it seems that this is much more common template tag then I thought.

ASP.NET - stackoverflow.com/a/649458
JSP - tutorialspoint.com/jsp/jsp_syntax.htm
eHaskell - hackage.haskell.org/package/ehaskell-0.7/ehaskell.cabal
eJS - ejs.co/#docs

As all of these are for HTML templates, I suspect if any of these were valid HTML that whatever compiles the templates to HTML would not be able to handle the conflicts.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. Review the project's existing ligature definitions and glyph conventions, then verify that <%, <%=, and %> are supported and render as intended without the reported template conflicts.

Written by the indexing model from the issue text.

Assessment

Tech stack
rails, ruby
Domain
design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.