nextcloud / nextcloud/fulltextsearch
json output for command fulltextsearch:search is not implemented
Open
Nobody has claimed this yet.
0. Needs triage
bug
- Dominant language
- PHP
- Stars
- 234
- Forks
- 64
- Avg merge
- 6h 18m
- Merged PRs (30d)
- 10
Description
How to use GitHub
- Please use the 👍 reaction to show that you are affected by the same issue.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Steps to reproduce
- Run
occ fulltextsearch:search --output=json admin samplestring - Observe the output
Expected behaviour
Output should be json-formatted
Actual behaviour
Output is not json-formatted
Server configuration
Latest version of Nextcloud and FullTextSearch apps to date, that is 31.0.7.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the occ fulltextsearch:search --output=json admin samplestring command through the fulltextsearch app's command entry point and output handling. Run the reproduction command to inspect its current output, then verify that the command emits valid JSON for the search request.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100