@flyboarder oh ok nice, so it's an "opt in" feature at this point?

@jjttjj don't you have to configure your dev tools to display debug level console logs?

@thedavidmeister correct, runtime specs are always opt in

Macro specs happen at expansion time

yeah i think this additional structure would make things easier to test

and just generally predict the behaviour of too

but it also might introduce new boilerplate too

like, using :toggle as an example, I can currently pass it any truthy value and not worry too much about it, in the new system i have to explicitly ensure that i'm passing true or false and even nil is not OK

Yes you are correct, although just like the attribute providers, you can always override the defaults, also nil should always be used to prevent an attribute from being applied IMO

@thedavidmeister I see what you mean about nil also not being ok, I'll refactor the specs to be nil-able.

@flyboarder yeah, if i send through nil i don't want to have to cast it to false every time

Right nil is always valid for the removal of the attribute