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
One thing I regret about picobox is that it uses non-conventional names for methods (e.g. pass_(), not inject) and classes (e.g. Box, not Container). I'm afraid it might be a too late to change the names.
That's why it's worth considering introducing some picobox.ext.enterprise extension that can expose better names.
Alternatively, the new interface can be developed in-house while deprecating the old one, which will delegate its calls to the new interface. 🤔 This approach will result in much more readable application code, though the project name will eventually lose its meaning.
One thing I regret about
picobox
is that it uses non-conventional names for methods (e.g.pass_()
, notinject
) and classes (e.g.Box
, notContainer
). I'm afraid it might be a too late to change the names.That's why it's worth considering introducing some
picobox.ext.enterprise
extension that can expose better names.How can it look like?
The text was updated successfully, but these errors were encountered: