Namespace support

[purge]

use a different name from 'sqwidget' for data-sqwidget components for fully conflict free use

[adhipg]

Sure, do we say something like data-config-* instead?

[purge]

No I mean the actual name is configurable. It's really low priority 

—
Sent from Mailbox for iPhone

On Tue, Oct 29, 2013 at 9:01 AM, Adhip Gupta [email protected]
wrote:

Sure, do we say something like data-config-* instead?

Reply to this email directly or view it on GitHub:
#97 (comment)

[adhipg]

Okay. That doesn't really matter. We can just send in everything data-* other than data-sqwidget (the widget url) to the widget as the settings. That means that the widget can decide what they want to use.

[zawilliams]

Is this actually in place to pull in data-*? I'm having trouble getting it to work. Would like to use this for a project and remove "sqwidget" in the embeddable code to keep a custom data attribute.

[adhipg]

We never got around to making this configurable. You need to use data-sqwidget-* to get items in config at present.
It should be relatively simple to change 'sqwidget' to something else.

I will possibly have a crack at fixing this over the weekend so that everything in data-* ends up in the config.