Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add apex code hightlight suport #1103

Merged
merged 11 commits into from
Sep 17, 2019
Merged

Conversation

malukenho
Copy link
Contributor

Apex is the programming language used by Salesforce.

@pyrmont pyrmont added needs-review The PR needs to be reviewed author-action The PR has been reviewed but action by the author is needed and removed needs-review The PR needs to be reviewed labels May 28, 2019
@pyrmont
Copy link
Contributor

pyrmont commented Jun 2, 2019

@malukenho Sorry, excuse my last message. I'll submit a review on your code now with some points to look at. It'll come through in a bit.

lib/rouge/lexers/apex.rb Outdated Show resolved Hide resolved
lib/rouge/lexers/apex.rb Outdated Show resolved Hide resolved
lib/rouge/lexers/apex.rb Outdated Show resolved Hide resolved
lib/rouge/lexers/apex.rb Outdated Show resolved Hide resolved
lib/rouge/lexers/apex.rb Outdated Show resolved Hide resolved
@pyrmont pyrmont self-assigned this Aug 26, 2019
@pyrmont
Copy link
Contributor

pyrmont commented Sep 1, 2019

Having now had the benefit of an extra three months as a Rouge maintainer, there were further changes to this lexer that I would recommend making beyond those identified in the 2 June review. Given how long it's been since the original submission, it felt like it made more sense to make those changes myself.

@malukenho I hope you don't mind me taking the liberty of force pushing the changes to your fork. I also hope all the changes make sense but please let me know if you have any comments. I realise now that this was very closely based on the Java lexer. I think my changes shouldn't cause issues but if you notice anything broken, let me know!

I will note that my version is slightly less flexible when lexing function definitions. I believe this should only be an issue for definitions that use spaces between the function name and the opening parenthesis (which I don't think is very common) and so don't expect this to be a problem in practice.

@pyrmont pyrmont merged commit a09305e into rouge-ruby:master Sep 17, 2019
@pyrmont pyrmont removed the author-action The PR has been reviewed but action by the author is needed label Sep 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants