[BLOSSOM-13] Use of configNode when creating dialogs Created: 15/Sep/10  Updated: 06/Dec/14  Resolved: 15/Sep/10

Status: Closed
Project: Blossom
Component/s: None
Affects Version/s: 1.1
Fix Version/s: 1.1.1

Type: Bug Priority: Minor
Reporter: Tobias Mattsson Assignee: Tobias Mattsson
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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
Date of First Response:

 Description   

A few discrepancies exists regarding the use of dialog config nodes.

  • When creating a dialog for a paragraph there is no config node, care must be taken not to pass along the config node for the editParagraph dialog.
  • When creating blossom managed dialogs the config node passed in is null, when in reality it should be the config node stored under /modules/blossom/dialogs/autodetected.
  • When TabBuilder creates dialog controls it passes the configuration node for the dialog to the init() -method of the controls. This is unnecessary and a potential source of undefined behaviour.


 Comments   
Comment by Jan Haderka [ 06/Dec/14 ]

Bulk close of old resolved issues.

Generated at Sun Feb 11 23:29:15 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.