Can I take Issue 46610 (Json output for occ)? Any Advice?

Hey, so I’ve decided to take on a NextCloud issue. 46610 looks like a good first issue.

I’ll admit that although I’m an experienced developer I’m a bit rusty with PHP, so figured that would be a good way to get back in the swing of things.

Any thoughts? Suggestions? If someone is willing to explain, I’m also curious what the “why” is behind the issue. That could help me fully flesh out how to resolve it, although (I realize this is a really small issue that can probably be fixed in fewer than 5 lines of code).

Thanks! Happy to be a part of the community!

hi @srcrr welcome to the forum :handshake:

this forum is primarily for private users support. Development happens completely on Github… AFAIK you are welcome to provide PRs… look at Github > Nextcloud > server > join the team

json output is much easier to parse. This makes it easier to process in scripted processes, such as for automation, monitoring, customization, etc.

Many occ commands already support json output mode (as hinted at in the follow-up comment on that issue). Ideally all occ commands will get there eventually.

Ah, apologies. The docs made it sound like development discussion should happen initially in here, but that may just be my perception. I’ll head on over to the good ol’ GitHub.

you are welcome happy to see more people are willing to support :handshake: