Why having a separate options objects on `registerBrush`

[dmarcos]

If there's not a good reason I would consolidate everything on a single object

[fernandojsg]

At first I thought about having the options + name as a single object, something like:

registerBrush({name: 'flat', spacing: 0.2}, definition);

But, following the registerXXX from AFRAME I changed it to include just the name as the first parameter. Another option could be to include the options themselves in the definition but as they're not really part of the definition, but options to properly setup the brush engine for that brush, I don't feel like a good idea to "pollute" the definition. Which options do you like more?