Skip to content
This repository has been archived by the owner on Aug 16, 2019. It is now read-only.

Register fallback components #8

Open
joanromano opened this issue Jan 19, 2017 · 6 comments
Open

Register fallback components #8

joanromano opened this issue Jan 19, 2017 · 6 comments

Comments

@joanromano
Copy link
Contributor

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.

@ChristianOrgler
Copy link

But what if there is no specified factory for a given type then we should just not show the component at all?

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? 😬

@joanromano
Copy link
Contributor Author

@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 View, where we might want to always fallback to simple cells or simple labels with text.

@ChristianOrgler
Copy link

I would not expect such kind of behaviour. Would this be on default?

@joanromano
Copy link
Contributor Author

@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 :/

@ChristianOrgler
Copy link

Can you elaborate a concret usecase where a fallback component would apply?

@joanromano
Copy link
Contributor Author

e.g show default labels whenever a specific component is not registered.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants