'defines' are activated with inverted booleans

[AntonioRedondo]

Hi Jetiny,

According to the documentation, given the below options:

{
  defines: {
    IS_SKIP: false,
    IS_REMOVE: true,
  }
}

The below input should produce the below output:

input

// #if IS_SKIP
  console.log('!Skip!')
// #endif
// #if IS_REMOVE
console.log('!Remove!')
// #endif

output

// #if IS_SKIP
  console.log('!Skip!')
// #endif

However the real behaviour is the opposite. In order to produce the output above described the configuration should be:

{
  defines: {
    IS_SKIP: true,
    IS_REMOVE: false,
  }
}

Actually I think the real behaviour is more intuitive than the one explained on the documentation. So the fix would suffice by just updating the documentation.

[AntonioRedondo]

Oops! Some wrong code was given mistaken results. Your code and documentation is perfectly fine! Closing this ticket.

[AntonioRedondo]

Sorry Jetiny, but after further testing it looks like actually, yes, the defines are activated in the opposite way. Could you double check this behaviour?

[brettz9]

I have the same problem...