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 newcomer to metloom, it is quite challenging to find specific classes or tests when trying to figure out execution logic. You can use your IDE (or preferred environment) to do a search and it sill leaves my head spinning when trying to navigate. Files also get quite long right now.
I am proposing three architectural changes/conventions:
File names to match their class
One class per file
Each class test file name corresponds with "test_my_awesome_class"
I have followed this pattern in the past and it makes code navigation quite simpler (especially for newcomers). It also makes testing each class simpler and organizes your test suite the same manner as your sources.
What do you guys think?
I am happy to prototype this in a PR
The text was updated successfully, but these errors were encountered:
As a newcomer to metloom, it is quite challenging to find specific classes or tests when trying to figure out execution logic. You can use your IDE (or preferred environment) to do a search and it sill leaves my head spinning when trying to navigate. Files also get quite long right now.
I am proposing three architectural changes/conventions:
I have followed this pattern in the past and it makes code navigation quite simpler (especially for newcomers). It also makes testing each class simpler and organizes your test suite the same manner as your sources.
What do you guys think?
I am happy to prototype this in a PR
The text was updated successfully, but these errors were encountered: