add archiver and app provider capabilities #2088
Conversation
|
Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would create a changelog item based on your changes. |
|
@wkloucek can you fix the linter error? |
|
@wkloucek is this ready for review? still marked as a draft PR. |
| @@ -110,6 +126,8 @@ type CapabilitiesFiles struct { | |||
| Favorites ocsBool `json:"favorites" xml:"favorites"` | |||
| BlacklistedFiles []string `json:"blacklisted_files" xml:"blacklisted_files>element" mapstructure:"blacklisted_files"` | |||
| TusSupport *CapabilitiesFilesTusSupport `json:"tus_support" xml:"tus_support" mapstructure:"tus_support"` | |||
| Archivers []*CapabilitiesArchiver `json:"archivers" xml:"archivers" mapstructure:"archivers"` | |||
There was a problem hiding this comment.
If there are multiple archiver or app provider versions available from the backend, how do I know which one is the most recent one? By parsing the versions? Or do you think it makes sense to introduce some MostRecent boolean in the respective capability struct?
|
In my PoC I'm using http://npmjs.com/semver to sort the available versions (which also works with strings like |
|
Merging it now. Other parameters can be added in separate PRs. |
No description provided.