-
Notifications
You must be signed in to change notification settings - Fork 59
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
Stop using class
for ‘singletons’
#87
Comments
+1 |
Even better? export function addClasses() { /*…*/ } |
Arguments against named exports:
Arguments for named exports:
|
I'll close this since it's very old. For now we're still using class for singletons, mainly because we want to allow overwriting methods, having the library be flexible. We can think about changing this later. If you think we should still discuss this for now, feel free to reopen this on metal/metal though. |
but this makes the code fragile and |
Using
instead of
does not bring all that value…
The text was updated successfully, but these errors were encountered: