[NPMCLI-85] cli commands for listing definitions Created: 27/Jan/17  Updated: 09/Feb/17

Status: Open
Project: Magnolia CLI
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: New Feature Priority: Neutral
Reporter: Matthias Müller Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to NPMCLI-65 Help users to choose areas and pages ... Open
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

It might be convenient to have cli commands for listing all existing page, component and maybe even area definitions in the current light module, optionally filtered by some provided string. It's quite difficult to remember all component paths correctly and this currently makes me switch to the editor of my choice to have a nice fuzzy-search over all yaml-files.



 Comments   
Comment by Christopher Zimmermann [ 09/Feb/17 ]

Nice idea.
Im wondering about the benefit vs confusion of showing the definitions in a certain scope.
Should it just show those in current light module? Or all of the light modules in the "light-modules" directory - or evenutally (Via REST or soemthing) all the definitions in the running instance?
Thoughts mmueller?

Comment by Matthias Müller [ 09/Feb/17 ]

Listing all definitions (maybe show warnings for incorrect definitions?) would be the most convenient solution, but also adds a dependency to a running magnolia instance and is probably more time consuming to implement. IMHO the developer will, in the majority of cases, search for definitions in the current light module. Therefore a simple, pure nodejs solution might be sufficient (especially as there is already a definitions app, which serves a similar purpose).

Comment by Christopher Zimmermann [ 09/Feb/17 ]

Thanks.

Generated at Mon Feb 12 04:46:23 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.