fossas/fossa-cli

The Ouput of fossa -o can be enhanced for better understanding.

Open

#231 opened on Aug 25, 2018

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Haskell (197 forks)batch import
component: cligood first issuehelp wantedsize: Mtype: ux

Repository metrics

Stars
 (1,488 stars)
PR merge metrics
 (Avg merge 8d 4h) (9 merged PRs in 30d)

Description

fossa -o produces a JSON file which may not be the best way to view it. Hence we cam consider enhancing the way it looks

Similar to issue #216 which talks about fossa -test . This could be inconvenient considering large projects , ex npm projects.

Contributor guide

Research direction
The issue requests a better output format for `fossa o` but provides no specific requirements. Review the current JSON output, and see if there are existing formatting options or libraries that could be used. Consider adding a human readable table or summary instead of raw JSON. Look at the similar issue #216 for `fossa test` for context. Since this issue is over 5 years old and lacks detailed discussion, it is best to first seek clarification from maintainers on what enhancement is desired.
Tech stack
None
Domain
clideveloper experiencetooling
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Unclear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20