Cannot use defines that have dashes about ifdef-loader HOT 4 CLOSED

so do you want to write

/// #if my-custom-define

and have it turned into

/// #if my_custom_define

?

I don't think that is possible because what comes after the #if is meant to be generic JavaScript expression.

Can you please explain your use case? Why not just use my_custom_define from the beginning?

from ifdef-loader.

From this example in the docs:

const opts = {
   DEBUG: true,
   version: 3,
   "ifdef-verbose": true,       // add this for verbose output
   "ifdef-triple-slash": false  // add this to use double slash comment instead of default triple slash
};

I think it's natural for people to define MY_UPPERCASE_DEFINE or my-lowercase-define, but my-lowercase-define doesn't currently work.

Perhaps incoming options should have dashes turned into underscores, automatically, so:

const opts = {
   DEBUG: true,
   version: 3,
   "ifdef-verbose": true,       // add this for verbose output
   "ifdef-triple-slash": false  // add this to use double slash comment instead of default triple slash
};

Would work with

/// #if ifdef_verbose

and

/// #if ifdef_triple_slash

The truth is that we are porting a library to JavaScript, which supports -Dlowercase-dashed-defines in the original language. Similar to the format of the ifdef-loader specific defines above, it would be nice to be able to preserve this for consistency of documentation... and don't dashes feel nice?

from ifdef-loader.

I agree that the docs are not very clear. ifdef-verbose and ifdef-triple-slash are not actual symbols available for #if, they are special switches used to configure the tool itself. And that's why they have - in their names: name clashing with user defined symbols isn't possible because they ain't valid JavaScript identifiers.

from ifdef-loader.

Oh yeah, I understand 😄

I just mean, ifdef-verbose feels nice. ifdef_verbose feels a little funny. I don't think these defines (themselves) are necessary in other source files, but a quick sanitize on the define names might be nice and make this pattern valid for user defines, too

from ifdef-loader.