EntityProperties
archetype prototype
#9258
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Visible
andInteractive
properties #9251As layed out in above ticket, we need to put
Interactive
andVisible
into an entity.This proposal (once fully propagated) solves everything noted in #9251 and additionally:
Drawbacks:
EntityProperties
is a pretty poor name since it's overly general and can be confused with everything else that's on an entity. Looking for something better.For discoverability, the central fbs definition file: