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
Scenario
A user wants refresh the local metadata (e.g. fetch any links (or replace broken links) since the last scrape). These metadata will be stored into a file locally (e.g. by default ~/.romie/db.json) acting as a database. The file's location should be specified into the configuration file (e.g. ~/.romie/romie.conf).
User Story
Given you have a configuration file, when you type romie update, then it will update your metadata.
Acceptance Criteria
Use the Cobra framework to create a romie update command.
Check if the configuration file exists. If the configuration file doesn't exist, it will error and exit.
Read a configuration file that will have a default location of the database file
Introduce a flag that the user will able to override the configuration file and point his own location of the db file.
Implement the necessary error checks (e.g. if the given location doesn't exit)
If the checking for the configuration file has not been implemented in the codebase yet, just create a file by yourself on your system, so you can work on this ticket.
If there are no metadata implemented in the codebase, just read the configuration file and make sure there is an entry for the database file and this file is accessible (read and write permissions).
The text was updated successfully, but these errors were encountered:
Scenario
A user wants refresh the local metadata (e.g. fetch any links (or replace broken links) since the last scrape). These metadata will be stored into a file locally (e.g. by default
~/.romie/db.json
) acting as a database. The file's location should be specified into the configuration file (e.g.~/.romie/romie.conf
).User Story
Given you have a configuration file, when you type
romie update
, then it will update your metadata.Acceptance Criteria
romie update
command.help
for the commandOptional: Use the https://github.com/spf13/afero for filesystem abstraction
Hints
If the checking for the configuration file has not been implemented in the codebase yet, just create a file by yourself on your system, so you can work on this ticket.
If there are no metadata implemented in the codebase, just read the configuration file and make sure there is an entry for the database file and this file is accessible (read and write permissions).
The text was updated successfully, but these errors were encountered: