Unsupported class names

[ghost]

Great module, and I got it working easily enough.

I'm currently importing the class names from bootstrap.less, and one of the classes is called in.

'in' is a reserved keyword and so causes a validation error in the bootstrap.less.d.ts file.

I had a look through the options, but there didn't appear to be an option that addresses this issue.

My 'webpack.config.js' section FWIW:

{
    loader: 'typings-for-css-modules-loader',
    options: {
        modules: true,
        namedExport: true,
        camelCase: true,
        sourceMap: true
    }
},

[ghost]

Don't use "in" as a class name seems the obvious answer, however it's part of bootstrap so I don't have control over that beyond "don't use bootstrap" which isn't much of an option.

A way to tell 'typings-for-css-modules-loader' to ignore any classes with reserved keyword names would be fine by me.

Or someway to have them automatically renamed.
e.g. "in" would become "reserved_in" or similar.

[timse]

hum good question - not sure if there is a way to make typescript ignore the "in" ?
e.g. by making it a string etc. - any ideas?

[scamden]

using non named exports is a workaround

[scamden]

except for me that's broken per #20

[aaronbeall]

@timse @scamden I posted in #20 but there is a way I believe we can export reserved words as top-level exports:

interface IFooCss { }
declare const styles: IFooCss;
export = styles;

This is basically commonjs compatibility syntax. If you want to expose IFooCss I think you can just wrap it in a namespace with the same name as the const.