[CAUSEWAY-975] [WON'T FIX] Allow the prototype facet to be associated with properties and collections, not just actions.

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Won't Fix
• Affects Version/s: viewer-wicket-1.7.0, core-1.7.0
• Fix Version/s: 2.0.0-M3
• Component/s: Core, Viewer Wicket
• Assignee: Unassigned
• Reporter: Daniel Keir Haywood
• Created: 12/Dec/14 10:14
• Updated: 19/Mar/20 16:59
• Resolved: 19/Mar/20 16:59

Description

Currently we have the ability to make actions into a prototype, meaning that they are only shown in prototype mode (-type SERVER_PROTOTYPE or Wicket development mode) and hidden during production mode (-type SERVER, or Wicket deployment mode).

Because of they way that they are implemented, contributed properties and contributed collections also "inherit" this prototyped-ness; they will also be hidden in prototype mode.

However, there is no way to hide regular (non-contributed) properties or collections when not running in prototype mode.

~~~
Don't think that this is a particularly significant issue, but it is an area of asymmetry in our metamodel so should probably be cleaned up, ie by introducing the notion of prototype for properties or collections.

This should be implemented as a new "prototype" attribute in @PropertyLayout and @CollectionLayout.

The Wicket viewer will need to honour this when rendering the entity forms (EntityPropertiesForm component etc).