-
Notifications
You must be signed in to change notification settings - Fork 6
Improve federation support #69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
If coming from a spec-compliant backend, `this.data.federation` is an object, so the function used to always return the empty array. The code now transforms the object into an array, and also adds the former object keys to each item as an `id` property.
Thanks automatic tests
@m-mohr Please check the additional commits I just added and then I think we could put a new version number and merge this? Or should we wait in case more changes become necessary while working on more stuff in the depending repos? |
I think we can merge this after resolving the comments, but should continue working on the other cases, e.g. jobs, services before we release. |
Okay, implemented your last recent comment. I didn't address the "couldn't find backendId" case in the JSDoc for lack of a good description plus not finding it too relevant anyway; if you happen to come up with a good text let me know. |
This adds
id
fields to the objects in the array returned bylistFederation
inCapabilities
, so that the backend details can be linked to what's infederation:backends
andfederation:missing
, which are just lists of IDs.Also, it fixes that
listFederation
used to always return the empty array, as it expectedfederation
to be an array, while it's actually always an object.