Magnolia CLI 3.0 additional tickets (DOCU-1321)

[DOCU-1339] More variables in CLI v3 Created: 20/Feb/18  Updated: 01/Mar/18  Resolved: 22/Feb/18

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Sub-task Priority: Neutral
Reporter: Martin Drápela Assignee: Martin Drápela
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
Template:
Date of First Response:
Sprint: Docu Sprint 43, Docu Sprint 44, Docu Sprint 45

 Description   

The following are missing on https://documentation.magnolia-cms.com/display/DOCS56/Prototypes+in+CLI+v3:

  • _dialog_
  • _fromUri_
  • _modelName_
  • _templateId_
  • _templateScript_
  • _toUri_

Already on the page:

  • _name_ This variable is replaced with the name of the item which is generated, for instance the name of a component template.
  • _lightDevModuleFolder_ This variable is replaced with the name of the current light module.


 Comments   
Comment by Christoph Meier [ 28/Feb/18 ]

mdrapela, jsimak - I have also reviewed and tested all the variables.
They all work - with one exception: _templateId is _not working for me.

Comment by Martin Drápela [ 28/Feb/18 ]

In the stock installation of CLI v3, the _templateId_ is used for generating blocks:

lib/config/mgnl-cli-prototypes/block/empty/blocks/__name__.yaml:2:templateId: __templateId__
lib/config/mgnl-cli-prototypes/block/_default/blocks/__name__.yaml:4:templateId: __templateId__
Comment by Christoph Meier [ 28/Feb/18 ]

I see, mdrapela - does this mean, that we must mention on all variables which one can be used for what?

I was astonished that _templateId_ is not working e.g. in am ftl-file for a page template.
However - I can use it in the ftl-file when creating a block.

Comment by Jaroslav Simak [ 01/Mar/18 ]

cmeier hmm, seems logical to have _templateId_ also available in page and component prototypes. I'll fill a ticket for that (NPMCLI-171).

Generated at Mon Feb 12 01:17:16 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.