[CONTEDIT-196] Configured blocks in an app(yaml) are not taken into account Created: 14/Nov/18  Updated: 19/Nov/18  Resolved: 19/Nov/18

Status: Closed
Project: Content Editor
Component/s: None
Affects Version/s: 1.1.5, 1.2
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Mercedes Iruela Assignee: Unassigned
Resolution: Not an issue Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Screen Shot 2018-11-14 at 17.08.57.png    
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

By default, stories.yaml is configured to allow just four kind of blocks:

blocks:
        - text
        - image
        - video
        - externalLink

But, in stories app you can use all the OOTB available blocks:

Also, if the definition is modified, for instance, to allow just one kind of block:

blocks:
        - text

Nothing changes and all the available blocks can be used.

NOTE: if no blocks are defined in the app yaml, the option of blocks should not appear.

Steps to reproduce:

  1. Go to Resources app and to stories.app file (/stories-app/apps/stories.yaml)
  2. Scroll down to the block's definition, see that for are defined (text, image, video, externalLink)
  3. Go to Stories app and see the options available in the block (6, see previous image).
  4. Go to Resources app and to stories.app file (/stories-app/apps/stories.yaml)
  5. Change configuration of the block section to allow just one type of block, for example text.
    blocks:
            - text
    
  6. Save and go to stories app, close it and open again, nothing changes.


 Comments   
Comment by Mercedes Iruela [ 19/Nov/18 ]

Not an issue, the configuration is taken into account as expected

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