Essential `om show`
Open
enhancement
- Dominant language
- Rust
- Stars
- 279
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
Follow-up to #147. We should improve `om show` such that it is useful across several projects.
Things to do:
- Display all that we can
- [x] #161
- [x] #163
- [x] https://github.com/juspay/omnix/issues/209
- [ ] #193
- [ ] https://github.com/juspay/omnix/issues/288
- [ ] #260
- [ ] #214
- [ ] Step 3 of #316
- [ ] ... ?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start at the `om show` CLI entry point and read #147 plus the unchecked follow-ups #193, #288, #260/#214, and step 3 of #316. Done is not defined beyond making `om show` useful across projects and completing the listed scope, so clarify which checklist item is being implemented before coding.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100