search

awatson1978 / meteor-api

Meteor API with tab completion and syntax highlighting.
MIT License
80 stars 17 forks source link

How to disable syntax highlighting #60

Open rizkysyazuli opened 9 years ago

rizkysyazuli commented 9 years ago

I'm pretty happy with my current syntax colour scheme. Is there a way to disable the additional syntax highlighting brought in by this package?

derwaldgeist commented 8 years ago

+1

It would be great if the additional syntax highlighting could be separated from the main package and put into a separate package. I'm having some troubles with the highlighter grammar, as it highlights texts that should not be highlighted (like the word Router in FlowRouter).

awatson1978 commented 8 years ago

I'm not completely opposed to separating them into different packages. I'd be more likely to change that architecture if we had a clear way to create metapackages with Atom's package manager.

As it is, we're making a push to create a unified IDE for clinical:METEOR using Atom, and FlowRouter (for instance) isn't currently on the roadmap. We need a one-stop location for that project, which this package is currently serving as.

In the short term, I'd recommend forking/clonding the package into your ~/.atom/packages directory, so you can make the custom changes to syntax highlighting. The Regexes aren't perfect, in part because the underlying API has changed over time. (Yet another reason we want to encourage the MDG to officially support a long-term-stable release.)

In the medium term, we need to research how to create meta-packages and packages-of-packages with apm.

In the long term, we'll break this apart and modularize it. But in the meantime, I need to keep the clinical:METEOR project as a priority.

derwaldgeist commented 8 years ago

@awatson1978 I can pretty much understand that you are focusing on clinical:METEOR, but I think you should in this case state a bit more clearly in the package description that this package is not meant for general purpose Meteor use. At the moment, this is a bit misleading, especially as it does not really support the latest API (e.g. the snippets create onRendered functions in a way that is not matching the current state, which makes them a bit useless for me). Yes, forking might be an option, will think about it.