Matthew Davidson
Matthew Davidson
I have a base module called 'experiment' basically representing the data model. 'experiment-edit' and 'experiment-render' both extend 'experiment'. I want 'Experiment', 'ExperimentEdit' and 'ExperimentRender' as my exportables.
Is this more like a plugin use case? Like, transform the name using an inflector?
@yields I understand that's a better way to do it, but I'm reorganizing another monkey's code and it's kind of a stop-gap TBH. I just don't want the current namespaces...
So this is how I'm doing it, ``` javascript module.exports = function (builder) { var standalone = builder.config.standalone, standalones = Object.keys(standalone), name = builder.local(), globalName = (standalones && standalones.indexOf &&...
Hmm. Upon testing, that gave me problems because a) `local` is an object not a string b) the appended `js` lives within the module scope, not global, so it doesn't...
I had the same issue, found the following hack worked ```jsx { // hack because isRowMaster isn't supported // @see https://github.com/ag-grid/ag-grid-enterprise/issues/221 if (!this.isRowMaster(rowNode)) { // assuming you have this function...
That doesn't make sense, you're not **enforcing** anything. No errors are thrown. It's silent failure. In any case, the ISO is a _recommendation_ whereas the above is a _spec_; the...
This is basically *my code should run even if it fails linting*.