You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So whenever we talk about this problem to someone interested in this project, I find myself using this idea of expressing a domain when we're writing html. I'm wondering if this terminology maps out well enough that it would make our code more clear to someone reading our code (rather than our docs).
The idea is simply that we have data-scopes, data-attr and finally we have data.
In html we have tags, attributes, and finally content.
I think if we used the word domain in our code whenever we're capturing some variable that might represent data-* or data it might become more clear since our code is already naturally going to have scopes that aren't necessarily dealing with data-scope, for instance.
Something as simple as matching domain-scope = "data-scope" might do just enough to make the code reading more clear to someone really trying to grok what we're doing here.
The text was updated successfully, but these errors were encountered:
So whenever we talk about this problem to someone interested in this project, I find myself using this idea of expressing a domain when we're writing html. I'm wondering if this terminology maps out well enough that it would make our code more clear to someone reading our code (rather than our docs).
The idea is simply that we have data-scopes, data-attr and finally we have data.
In html we have tags, attributes, and finally content.
I think if we used the word domain in our code whenever we're capturing some variable that might represent data-* or data it might become more clear since our code is already naturally going to have scopes that aren't necessarily dealing with data-scope, for instance.
Something as simple as matching
domain-scope = "data-scope"
might do just enough to make the code reading more clear to someone really trying to grok what we're doing here.The text was updated successfully, but these errors were encountered: