I noticed in the merge [#9] for the layout header component that two empty .tsx files have been added to the code. I assume that these files are supposed to be placeholders for pages to be filled out in a later user story, therefore becoming part of a new route. If this is the case then this is the wrong method for doing so. Instead a new directory in the app directory should be made with an appropriate name for the purpose of the page. For example, "visualization". Inside of what are considered as routing directories a page.tsx file should be made which works as an index.html file if you are familiar with that system. Essentially it is a naming convention that informs the browser to render that .tsx file first when entering the route http://localhost:3000/visualization.
These files should either be changed to routes in the manner described above or removed entirely since they are empty and create clutter not necessary to the current sprint goal of creating an MVP
I noticed in the merge [#9] for the layout header component that two empty .tsx files have been added to the code. I assume that these files are supposed to be placeholders for pages to be filled out in a later user story, therefore becoming part of a new route. If this is the case then this is the wrong method for doing so. Instead a new directory in the app directory should be made with an appropriate name for the purpose of the page. For example, "visualization". Inside of what are considered as routing directories a page.tsx file should be made which works as an index.html file if you are familiar with that system. Essentially it is a naming convention that informs the browser to render that .tsx file first when entering the route http://localhost:3000/visualization.
These files should either be changed to routes in the manner described above or removed entirely since they are empty and create clutter not necessary to the current sprint goal of creating an MVP