Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Internal variable naming ideas/conventions RFC #9

Open
dgmcguire opened this issue May 18, 2016 · 0 comments
Open

Internal variable naming ideas/conventions RFC #9

dgmcguire opened this issue May 18, 2016 · 0 comments

Comments

@dgmcguire
Copy link
Contributor

dgmcguire commented May 18, 2016

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant