chapel-lang / sphinxcontrib-chapeldomain

61%

master: 60%

LAST BUILD ON BRANCH 0.0.18

branch: 0.0.18

CHANGE BRANCH

x

Reset

• 0.0.18
• 0.0.10
• 0.0.11
• 0.0.12
• 0.0.13
• 0.0.14
• 0.0.15
• 0.0.16
• 0.0.17
• 0.0.19
• 0.0.2
• 0.0.20
• 0.0.3
• 0.0.4
• 0.0.5
• master

Build # 148

Build Type

push

travis-ci

Committed by web-flow

Commit Message

Merge pull request #41 from e-kayrakli/pygments-improve-lexer

Improve the custom pygments lexer

This PR:

- Refactors large tuples into their own variables
- Adds a new `receivertype` state to handle
<img width="553" alt="Screen Shot 2020-11-19 at 10 00 25 AM" src="https://user-images.githubusercontent.com/4141670/99705104-2581a080-2a4e-11eb-8727-957097d03e6a.png">

by properly highlighting it including the keywords within parentheses:

<img width="540" alt="Screen Shot 2020-11-19 at 10 00 44 AM" src="https://user-images.githubusercontent.com/4141670/99705166-3500e980-2a4e-11eb-9407-3e18ac2c3ce3.png">

We can tweak how we handle secondary methods better, but this PR doesn't do that. For example we can't currently higlight without this patch:

<img width="606" alt="Screen Shot 2020-11-19 at 10 03 54 AM" src="https://user-images.githubusercontent.com/4141670/99705429-9032dc00-2a4e-11eb-9379-fcd615efe7c9.png">

With this patch, we can highlight, but a non-parenthesized receiver type shouldn't be higlighted as function name
<img width="583" alt="Screen Shot 2020-11-19 at 10 05 06 AM" src="https://user-images.githubusercontent.com/4141670/99705563-bfe1e400-2a4e-11eb-88ea-27274f2a0420.png">

I wasn't able to get that puzzle solved in a reasonable amount of time, but I think this is still progress. At least we don't have to workaround this issue when writing `code-block`s in docs.

[Reviewed by @lydia-duncan]

Run Details

494 of 805 relevant lines covered (61.37%)

0.61 hits per line