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
Surely it's easy enough to use directory p.dirname. However, I have a lambda that is also used as a rule dep (to ensure the parent directories are created). I was hoping to use the same lambda when iterating over the array_of_pathnames.
@hsbt Is there any discussion thread on why the pathmap extension was removed from Pathname?
I could understand if the eventual goal is to remove it from String as well. Though as long as String has it, I'd expect Pathname to have it as well? If the eventual goal is to remove the extensions entirely (or perhaps make them opt-in?) should it be removed from both String and Pathname at the same time so the interfaces remain consistent?
The rake docs here still indicate that
Pathname#pathmap
exists. However, it was removed by #130It would be easy enough to fix the docs. But perhaps a different question is, why was this removed from Pathname?
I expected the following to work, but instead got
NoMethodError: undefined method 'pathmap' for #<Pathname
Surely it's easy enough to use
directory p.dirname
. However, I have a lambda that is also used as a rule dep (to ensure the parent directories are created). I was hoping to use the same lambda when iterating over the array_of_pathnames.As long as we're extending String, I'd expect the same extensions to work on the "more domain appropriate" Pathname.
The text was updated successfully, but these errors were encountered: