Motivation
We use different API entries for specifying output folders and files and it seems we should study the Dart methodology for URI so we can be more consistent.
From module_services_api review:
I like this API because it's easy to understand, but should we be using some sort of URI object or something from Dart instead that supports referencing files, directories, and other weird stuff instead? I'm not sure the answer, genuine question.
Desired solution
Consistent file resource specification for all output routines, including file directory specification, file name, extension, module name matching, etc.
Alternatives considered
No response
Additional details
No response
Motivation
We use different API entries for specifying output folders and files and it seems we should study the Dart methodology for URI so we can be more consistent.
From module_services_api review:
I like this API because it's easy to understand, but should we be using some sort of URI object or something from Dart instead that supports referencing files, directories, and other weird stuff instead? I'm not sure the answer, genuine question.
Desired solution
Consistent file resource specification for all output routines, including file directory specification, file name, extension, module name matching, etc.
Alternatives considered
No response
Additional details
No response