The folder structure for how and where the code lives is an artifact from a refactor that happened a very long time ago (hence a folder called apiv2). This folder structure should be cleaned up and improved. For example:
there should not be a folder called pyblazing inside another folder called pyblazing.
there should not be a folder called apiv2.
This particular task should be done as a singular PR where it just moves files, but minimizes that amount of actual code changed, which way we avoid nasty merge conflicts.
The folder structure for how and where the code lives is an artifact from a refactor that happened a very long time ago (hence a folder called apiv2). This folder structure should be cleaned up and improved. For example:
pyblazinginside another folder calledpyblazing.apiv2.This particular task should be done as a singular PR where it just moves files, but minimizes that amount of actual code changed, which way we avoid nasty merge conflicts.