owlcollab / owlcollab/owltools
Should TableRenderer include properties?
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 115
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
TableRenderer seems to output only classes and instances. Is there a reason to exclude properties?
Contributor guide
No contributing guide indexed for this repository
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 reading OWLTools-Core/src/main/java/owltools/io/TableRenderer.java at the linked lines and inspect how its current output scope is defined. Determine the intended treatment of properties with maintainers, then use any existing renderer checks to verify the agreed behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100