-
Notifications
You must be signed in to change notification settings - Fork 4
Register fallback components #8
Comments
But what if there is no specified factory for a given So if we there exists a new json file which includes a new component which is not supported by an older app version it should just not show it at all. Wait, do I get the point you mean? 😬 |
@ChristianOrgler if there is no default component and a given type is not registered, we will not show it. If there is a default component, we will show that default component whenever a type is not registered; the clients can choose. I think that might be useful for component types like |
I would not expect such kind of behaviour. Would this be on default? |
@ChristianOrgler what wouldn't you expect? Sorry I am bit confused since you are commenting something from a month ago and not giving enough context :/ |
Can you elaborate a concret usecase where a fallback component would apply? |
e.g show default labels whenever a specific component is not registered. |
We may want to add te ability to register fallback components in JSONFactory whenever there is no specified factory for a given
type
key.So eg. for clusters always fallback to stacks.
The text was updated successfully, but these errors were encountered: