Open srid opened 4 years ago
each source in its own file I believe is overkill, but i'm open to the idea of supporting several sources.json
s. Definitely worth consideration!
from the user
perspective it would be nice to have everything in one file to have an overview above all in one place
but as developer
I prefer to change only one file and commit that change (fully visible) to the repo in git(hub)
I would prefer a logic/semantic e.g.
if there exist files like source__vscode.json
- those will be combined with source__pkgs.json
to source.json
before the import
-- [and check for duplicates in pname ]
then the process stays the same but there offers full flexibility.
I would like to have each source to be defined in its own file (
sources/foo.json
,sources/bar.json
, ...) so that git history is much easier to deal with it. Has this been thought of before, and if not is it worth a consideration?