Context Navigation

Changes between Initial Version and Version 1 of Ticket #49196, comment 15

-                      initial
+                      v1
 > I wasn't aware that the file location might be treated as a contract. If this is the case then we can consider keeping the current names and handle the rest differently.
 Yeah, for better or for worse pretty much all files in WP are not "source" files, they are "production" files. "Architectural changes" like moving and/or renaming them is usually not a good idea :)
+Yeah, for better or for worse pretty much all files in WP are not "source" files, they are "production" files. "Architectural changes" like moving and/or renaming them are usually not a good idea :)
 That's the reason why all the old js is moved back to the previous places when building, from `/scr/js` to `/build/wp-admin/js` and `/build/wp-includes/js`
 …
 > Another option would be to proxy old locations to the new one.
 Yes, that's possible. Would probably require to keep the existing files but then delete all the code there and just add `include [path to the moved/renamed file]`. However thinking this is a "last resort" solution for when a file has to be moved and there's absolutely no other way to do it.
+Yes, that's possible. Would probably need to keep the existing files but then delete all the code there and just add `include [path to the moved/renamed file]`. However thinking this is a "last resort" solution for when a file has to be moved and there's absolutely no other way to do it.