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
The goal here is to make it clear when an absolute path is being used. There are some challenges in making this work, but largely it should be possible. There is also one potential benefit from this as well:
(virtual / non-virtual components). For an absolute path, it would be useful to distinguish the "virtual" segments from the non-virtual segments. This would allow us to generate a valid context directly from an absolute path, rather than carrying around the context separately.
From a terminology perspective, we could call them: static vs dynamic or outer vs inner, etc. They do remind me somehow of Java inner classes.
For a relative path, separating the virtual and non-virtual components perhaps doesn't matter since we cannot use this information anyway.
The text was updated successfully, but these errors were encountered:
The goal here is to make it clear when an absolute path is being used. There are some challenges in making this work, but largely it should be possible. There is also one potential benefit from this as well:
From a terminology perspective, we could call them: static vs dynamic or outer vs inner, etc. They do remind me somehow of Java inner classes.
For a relative path, separating the virtual and non-virtual components perhaps doesn't matter since we cannot use this information anyway.
The text was updated successfully, but these errors were encountered: