Fix managed resources #28
Conversation
| (condition) => condition.type === 'Ready', | ||
| ); | ||
| managedResources | ||
| ?.filter((managedResource) => managedResource.items) |
There was a problem hiding this comment.
It’s just this
There was a problem hiding this comment.
this prevents crashing and therefore fix the bug but would silently ignore the error. So if a resource cant be queried because of e.g. rate limiting, the user would expect to see its resource and would be confused. I think we should indicate this somehow that we failed to query certain resources.
True, we should keep this in mind when we move to the new backend. |
2 participants
This PR fixes an issue with the managed resources when the server response contains an error and the
itemsfield ist not included.