Replies: 1 comment 3 replies
-
|
@stdedos in the legacy output (the default), the default behavior is to print out the ID and what we call the I'm not sure what the decision behind the short vs. verbose behavior was as it's before my time. YAML would probably make more sense and just print it all out, but that pulls in another (currently optional) dependency for the CLI. |
Beta Was this translation helpful? Give feedback.
-
|
... or JSON and avoid the extra dependency 🙃 Could we extend the config file with a global (and per-server?) option |
Beta Was this translation helpful? Give feedback.
-
|
I guess JSON is more for programmatic use so might not be the nicest output by default 😅 Yes, a global config option might be best actually. |
Beta Was this translation helpful? Give feedback.
-
I just "don't want to remember this" anymore 😅 Maybe I'm a minority, but I'm using the CLI solely as the "quick" version of Legacy format (if extended) may make sense. Idk the amount of "ready formats" vs "not-ready" (like my command's case). If not-ready is a majority, it's better IMHO to switch to YAML (if you are fine for the dependency). Honestly, I was "mislead" thinking that I can pass posargs to the command and get the keys I wanted 😅 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I am trying to probe the https://docs.gitlab.com/ee/api/merge_requests.html#get-single-mr API, and I thought I'd use
python-gitlabfor this.After some trying, I got to
I expected "some kind of output". However, I only received
iid: 15899- which I kinda new already 😕I needed to add
-vto see "some kind of output". Then, I noticed-o json, and I got something of what I wanted.... However, why isn't that the default? I don't want to start a "default output format" religious war - but some kind of output, that's not what I needed to spoon-feed in the first place
What am I missing here?
Beta Was this translation helpful? Give feedback.
All reactions