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
Would it be a good idea to allow prefix classes/types as arguments in addition to a specific command (or list of)? My concern is that it is not straightforward to extend if I want other prefixes (not necessarily defined in the package) to be accepted as well.
For example, I have defined a prefix class with a custom transient-init-scope method. The expectation is that any prefixes of this class/type will use the format from this transient-init-scope. It thus seems desirable to allow transient-scope to return a non-nil value if a prefix matches that type.
Alternatives for this use case that don't require changing the current implementation:
Define a list variable for "compatible prefixes" that can be added to by the user or external packages.
It might also work to add some hook/method-with-qualifier to the prefix class that automatically does this.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Would it be a good idea to allow prefix classes/types as arguments in addition to a specific command (or list of)? My concern is that it is not straightforward to extend if I want other prefixes (not necessarily defined in the package) to be accepted as well.
For example, I have defined a prefix class with a custom
transient-init-scope
method. The expectation is that any prefixes of this class/type will use the format from thistransient-init-scope
. It thus seems desirable to allowtransient-scope
to return a non-nil value if a prefix matches that type.Alternatives for this use case that don't require changing the current implementation:
Beta Was this translation helpful? Give feedback.
All reactions