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
I'm wondering, can we get things more correct by doing transformations (like suffixifying, relativizing) later than we do; passing in the currentPath at the last minute?
Or maybe something different.
This could improve or close a bunch of output issues:
aryairani
changed the title
rethink absolute/relative/suffixified/non-suffixified
rethink absolute/relative/suffixified/non-suffixified/hash-qualified
May 13, 2020
I'm wondering, can we get things more correct by doing transformations (like suffixifying, relativizing) later than we do; passing in the
currentPath
at the last minute?Or maybe something different.
This could improve or close a bunch of output issues:
delete
unexpectedly shows aliases outside of current namespace #1284 diff after delete shows external aliasesupdate
output uses non-suffixified PPE #1273 update uses non-suffixified ppeview
/display
? #1241 /view
should be smarter about resolving names #1071 add suffixed-based name resolution forview
/display
pull
misses necessary namespace prefix #957 suggested command in Tip about name conflict afterpull
misses necessary namespace prefixDesign may be informed by:
view
could use some logic for preferring the user provided name #977 bias names in output according to inputadd
andupdate
commands can allow definitions that start with.
#553 letadd
/update
support new definitions with absolute namesThe text was updated successfully, but these errors were encountered: