alunny on master
v1.5.2 (compare)
alunny on v1.5.2
v1.5.2 (compare)
angus-c on master
publish lib and index to npm Merge pull request #378 from fl… (compare)
alunny on publish_lib
publish lib and index to npm (compare)
So I'm looking to switch from a in-house framework to Flight, they're very similar except that Flight is obviously supported by many more developers. I had a question about attributes though.
In our in-house solution we define defaultAttributes as:
{ events: {
'bob': 'blahblah',
'bill': 'bloobloo' },
selectors: {
'anne': 'meepmeep',
'ariel': 'moopmoop' },
...
}
as opposed to flight which suggest defining the defaultAttributes as:
{ 'bobEvent': 'blahblah',
'billEvent': 'bloobloo',
'anneSelector': 'meepmeep',
'arielSelector': 'moopmoop',
...
}
We found that the Flight standard is very verbose. and results in a lot of repetition in our code. Is this really the best practice? We've thought about creating a mixin which will use 'selector.'
for .select()
but that seems really hacky and I would rather not have to do that.
Thoughts?