Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Expose all required fields in container listings for the filesystem backend
See original GitHub issueContainer listings detail all resources within a container, and add some metadata for each.
With the acceptance of https://github.com/solid/specification/pull/352, we have determined that 4 pieces of metadata need to be present per item as per the 0.9 specification
rdf:typewithhttp://www.w3.org/ns/iana/media-types/{+iana-media-type}#Resourcestat:sizedcterms:modifiedstat:mtime
This functionality is currently implemented in an external module https://github.com/RubenVerborgh/solid-metadata-extender, but given that it is now part of the 0.9 spec, we need to move this to the main codebase.
Additionally, I would suggest that we write the corresponding tests for https://github.com/solid/specification-tests
Issue Analytics
- State:
- Created 2 years ago
- Comments:10 (9 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
ResponseMetadatais specifically used for metadata that was generated as part of a response, and should not be stored in a resource. The ones above are generated on a higher level and should be stored. It’s just that the file data accessor stores them by how the file system works, but the other data accessors store those as actual metadata.Potentially that we need to rethink some things there after the metadata PR is finished.
Added in #1237. Will be part of v4.0.0