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
We have a handful of files at the root of /src that should probably be organized to sub-directories. E.g., map-proposals.ts (and its testfile) should go in /src/utils.
Let's do a pass over that on a rainy day.
The text was updated successfully, but these errors were encountered:
@reefdog just for some context there was a local MO to avoid a generic /utils directory, with the idea being that it becomes an antipattern / a disorganized cluster of otherwise unrelated functionality, and it would be better to try to keep things in well-named groups, either as root level files OR (as things expand) in folders.
This is why in /service we don't have a utils directory but we DO have a series of named folders and a few root level code files (e.g. logger is a root level concept).
I'm not actually trying to strongly advocate against a utils though the merits of the idea seemed strong enough to at least give it a whirl at the time!
@slifty That's a good note. I do think something as specific as map-propposals.ts doesn't need to be at src/, but am definitely open to a finer organization than just utils/
We have a handful of files at the root of
/src
that should probably be organized to sub-directories. E.g.,map-proposals.ts
(and its testfile) should go in/src/utils
.Let's do a pass over that on a rainy day.
The text was updated successfully, but these errors were encountered: