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

Rename operator interfaces #216

Open
appsforartists opened this issue May 3, 2017 · 1 comment
Open

Rename operator interfaces #216

appsforartists opened this issue May 3, 2017 · 1 comment

Comments

@appsforartists
Copy link
Member

At some point, we had a convention that interfaces should end with able; hence, all the operator interfaces, e.g. MotionMemorable. That convention hasn't really held true - both MotionObservable and the interactions are examples of concrete classes that end in able.

Thus, we should clean up the interfaces to better distinguish them. The winning proposal so far is to capitalize the operator name, e.g.:

withPluck(): S & Pluck {
  return class extends superclass implements Pluck {
    pluck() // ...

withRemember(): S & _Remember {
  return class extends superclass implements _Remember {
    _remember() // ...
@appsforartists
Copy link
Member Author

Another option is to rename the interactions to avoid the able suffix. That should probably happen too, since most compound interactions won't lend themselves easily to "$VERBable" names.

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

No branches or pull requests

1 participant