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
It gets super confusing when you have multiple aux methods with the same dispatch value, and it can lead to weird gotchas if you rename a namespace or remove them. It's also indeterminate which order they're applied in...
I think there are some valid use cases for things like multiple :around :default methods for logging and other things like that. How can we still support that case?
Maybe we should make the unique key something you can optionally supply yourself, and by default it's nil. So if you want to do something weird you can supply a unique key to prevent it from getting stomped on. Altho I'm not sure that would really solve the renaming namespaces issue.
The text was updated successfully, but these errors were encountered:
It gets super confusing when you have multiple aux methods with the same dispatch value, and it can lead to weird gotchas if you rename a namespace or remove them. It's also indeterminate which order they're applied in...
I think there are some valid use cases for things like multiple
:around :default
methods for logging and other things like that. How can we still support that case?Maybe we should make the unique key something you can optionally supply yourself, and by default it's
nil
. So if you want to do something weird you can supply a unique key to prevent it from getting stomped on. Altho I'm not sure that would really solve the renaming namespaces issue.The text was updated successfully, but these errors were encountered: