I think your best bet is to copy the camel case rule into a custom rule and
modify it to do what you need. We don't really have any way to do a
fallback like you described.

-N
On Fri, Sep 16, 2016 at 2:00 PM 'Charlie Andrews' via ESLint <
eslint@googlegroups.com> wrote:

> We're working on integrating eslint into the open source codebase that I
> work in <https://github.com/catapult-project/catapult>, and we love it so
> far!
>
> I had a quick question about how to alter the behavior of another rule. In
> our codebase, we have a convention of adding an "opt_" prefix before
> optional parameter names. In all other regards, we follow the eslint
> camelcase rule <http://eslint.org/docs/rules/camelcase>.
>
> Does anyone have a recommendation on how to implement an eslint rule that
> defers to camelcase except in that situation?
>
> --
> You received this message because you are subscribed to the Google Groups
> "ESLint" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to eslint+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"ESLint" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to eslint+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to