Settings needs to make category rdfs:subClassOf its classification
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 7
- Forks
- 3
- Avg merge
- 7m
- Merged PRs (30d)
- 3
Description
Tableview columns appear blank for custom classifications created with settings.
This can be fixed manually by adding rdfs:subClassOf definitions, e.g.
:id1625386228650 rdfs:subClassOf :id1625386215075.
:id1625386377799 rdfs:subClassOf :id1625386215075.
where settings had created:
:id1625386215075
rdfs:label "Task categories";
owl:disjointUnionOf
( :id1625386228650 :id1625386377799).
This is necessary because renderTable queries for rdfs:subClassOf, not owl:disjointUnionOf:
https://github.com/solid/issue-pane/blob/a213104dfb997a4592f5ff3fe82c2cc6d85a5f8c/issuePane.js#L275-L279
Presumably the fix will involve adding a statement to trackerSettingsForm.ttl, probably in core:CategoryForm
https://github.com/solid/issue-pane/blob/a213104dfb997a4592f5ff3fe82c2cc6d85a5f8c/trackerSettingsForm.ttl#L97-L116
However, I'm not yet sure how solid-ui would specify this, and a similar problem has already been raised for states (issue #22), which are optionally specified as rdfs:subClassOf wf:Open
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 in issuePane.js around renderTable at lines 275-279 to confirm the rdfs:subClassOf query, then inspect core:CategoryForm in trackerSettingsForm.ttl at lines 97-116. Compare the category RDF generated by settings with the manually added subclass statements and the related states issue #22. Done means custom classifications created through settings render their columns in the tableview.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100