-
Story
-
Resolution: Won't Do
-
Major
-
None
-
None
-
None
-
-
Empty show more show less
-
HL & LD 3
-
1
Update:
- Validate support for references/link-fields from new UI FW app to new UI FW app
- We will not introduce support for referencing new content-apps from old ones. Especially since new apps are now the default with the !content-type directive.
Original description (oldie)
As a developer I want to use CT definition to generate apps that are compatible with 6.1, so that I can be productive in 6.0
Acceptance criteria
- In 6.1 I can "retrofit" existing 6.1 style apps to have CT, so that other CT definitions can reference them.
- A developer can create a CT based app with a reference field which references the V8-contacts app.
Example of the second case.
- Categories app is changed to be a new V8 style app.
- I create new "Cars" app that has a reference to the "Categories" content type.
- I can create a new Categories content type which "retrofits" that V8 style content app.
Acceptance criteria
- depends upon
-
MGNLUI-5913 Problems with references in m6 content-type generated apps
- Closed
- is causing
-
MGNLCT-151 DOCS: Document that an M6 CT-app cannot 'reference' an M5-CT app
- Closed
- is depended upon by
-
MGNLCT-102 DOC: Retrofit existing apps with a content type
- Open
- relates to
-
MGNLUI-4962 Provide graceful and clear way of transition to the new version of the UI framework
- Closed