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
As a developer I find there is a much greater likelihood of breaking something inadvertently when using long relative path names with ../../../ to get to the proper directory location. I would expect for these files to be co-located with the other code files that they correspond to (especially tests).
Needed Changes:
- Co-locate test files with the target file, but inside a tests directory.
- Create a package.json file for all OCAPI library files (/lib subdirectory).
- Add the library as a package to the dependencies of the base project.json file.
-- This will allow for all of the lib files to be included without needing to traverse up the directory tree before specifying the path of a file that is needed.
- Update all references to the lib files to reference them with the new package notation.
The text was updated successfully, but these errors were encountered:
As a developer I find there is a much greater likelihood of breaking something inadvertently when using long relative path names with ../../../ to get to the proper directory location. I would expect for these files to be co-located with the other code files that they correspond to (especially tests).
Needed Changes:
-- This will allow for all of the lib files to be included without needing to traverse up the directory tree before specifying the path of a file that is needed.
The text was updated successfully, but these errors were encountered: