4 ms·
Right, and then HTML/CSS ids and classes further muddy the waters. It's usually worth keeping at least your model attributes with the same name, from DB column
by jashkenas 17y ago
Right, and then HTML/CSS ids and classes further muddy the waters. It's usually worth keeping at least your model attributes with the same name, from DB column through Web App to JS. So we do:
doc.set({related_article : 'http://...'});
Even though you might have:
doc.openRelatedArticle();
As a method on the JS model. Definitely less than ideal.