Check of the usefulness of the Layer properties

[gchoqueux]

In Layer class two properties aren't, may be, usefulness.

in constructor:

1. this.options

this.options = config.options || {};

config.options has been almost removed since the creation of the sources, so it doesn't have much senses to keep it.

2. Object.assign(this, config)

This assignment exists to not forget layer properties. It would assume and document all properties and not used Object.Assign.

[mbredif]

Feel free to simplify things, but please keep something that is extensible by design ! (support custom layers with custom properties, custom sharders...)

[zarov]

config.options has been almost removed since the creation of the sources, so it doesn't have much senses to keep it.

Ok for deprecating this.options.

This assignment exists to not forget layer properties. It would assume and document all properties and not used Object.Assign.

I'm for removing this too, we need to complete the documentation first though.

Feel free to simplify things, but please keep something that is extensible by design ! (support custom layers with custom properties, custom shaders...)

Yes for extensible design: all properties of a layer, source etc... are accessible after instantiation. Is there a case where this would cause problems ? (for example in the init of a certain type of layer ?)