-
Notifications
You must be signed in to change notification settings - Fork 1.2k
explore/record should write to ~/.opencli/ instead of cwd #711
Copy link
Copy link
Open
Description
Problem
explore and record write output to .opencli/ relative to cwd, while operate init correctly writes to ~/.opencli/clis/. This inconsistency pollutes project directories with opencli artifacts.
Current behavior
| Command | Output path | Correct? |
|---|---|---|
operate init |
~/.opencli/clis/<site>/ |
✅ |
explore |
cwd/.opencli/explore/<site>/ |
❌ |
record |
cwd/.opencli/record/<site>/ |
❌ |
Source references:
explore.js:329:path.join('.opencli', 'explore', siteName)— relative pathrecord.js:625:path.join('.opencli', 'record', site)— relative pathrecordhas--out <dir>as workaround, butexploredoesn't exposeoutDirin CLI args (only in code)
Expected behavior
Default output for all commands should go to ~/.opencli/:
~/.opencli/explore/<site>/~/.opencli/record/<site>/
This is consistent with operate init writing to ~/.opencli/clis/ and keeps project directories clean.
Workaround
record:opencli record <url> --out ~/.opencli/record/<site>explore: no workaround (need tocd ~/.openclifirst)
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels