-
Notifications
You must be signed in to change notification settings - Fork 0
refactor: use shopen instead of manual launch_editor #4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -35,6 +35,7 @@ dependencies = [ | |||||
| "platformdirs", | ||||||
| "pydantic", | ||||||
| "python-dateutil", | ||||||
| "shopen >= 0.2.2", | ||||||
|
||||||
| "shopen >= 0.2.2", | |
| "shopen>=0.2.2", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The new
config editpath now depends on callingshopen.open(...), but there doesn’t appear to be any automated test covering this behavior (the existing CLI bats tests cover other commands but notconfig edit). Please add a test that exercisesgcalcli config editwhile stubbing/monkeypatchingshopen.openso the test can assert it’s invoked witheditwithout launching a real editor, and that the config file is created when missing.