Configuration options for angular integration

[jperl]

Right now I have this line commented out because the application already uses angular.mock.e2e.$httpBackendDecorator and the mocks get overridden if I leave it there.

It would be a nice to be able to pass configuration options to features.

[tbosch]

Yes, good idea. What do you think about the following:

• boolean features: Just as today, just use feature('someFeature') to enable it
• features with config: Use an object hash, e.g. feature({name: 'someComplexFeature', configProp1: 1, ...}

By this, we can still pass multiple features to one call of feature.

Tobias

[jperl]

I like that a lot

[jperl]

What about instead: feature(name, [config]). Config would be an optional parameter so you could call

• boolean features: feature('someFeature')
• features with config: feature('someFeature', { configProp1: 1, ... })

That way you do not need to pollute the config with a name property and you can call it the same way as now.

[tbosch]

Yes, true. However, right now, feature accepts a list of features, e.g. feature('xhrSensor', 'timeoutSensor', ...). To keep this property, the object notation would be better... Mmmh..

Tobais

[jperl]

Got it that makes a lot of sense. I agree with feature({name: 'someComplexFeature', configProp1: 1, ...}