Closed cuixq closed 2 weeks ago
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 65.29%. Comparing base (
72afdb8
) to head (d9b037c
).
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
For now, this flag is only valid when experimental-offline
is set. The motivation is that experimental-offline
and experiment-local-db
is confusing, so we are trying to separate the offline part and the download part.
I think ideally, we can have some subcommand for example download
to handle downloading the database, and I like the idea to specify the systems to download in the command!
Is the intention for this feature to be used independently of a scanning run, or as part of one? Would it be possible to include another flag that accepted a subset of ecosystems to download
@andrewpollock I proposed basically this exact thing in subcommand form at our weekly catchup 😄
My thinking is especially now that we have both subcommands and interactive-ness, we could provide a very nice interface for managing these databases and their location without overloading scan
with a lot of flags
Part of me now wonders if it could be worth having a dedicated offline
subcommand instead of a flag? but maybe that's just trading a (flag) swing for a (subcommand) roundabout?
I personally think download-offline-databases
makes more sense than offline-download-databases
.
@G-Rath do you mind taking another look? Thanks.
Currently flags
experimental-offline
andexperimental-local-db
are confusing sometimes.This PR renames
experimental-local-db
toexperimental-download-database
to make it more explicit whether to download the database or not.For now,
experimental-download-database
only works whenexperimental-offline
is set.internal/local
is also modified to reflect the change in the naming and meaning of this flag.