Details

    • Type: Bug Bug
    • Status: InputQ
    • Priority: High High
    • Resolution: Unresolved
    • Affects Version/s: 1.8.1, 1.9.0, 1.7.3
    • Fix Version/s: 1.9.1, 1.7.4, 1.10.0
    • Component/s: Platform > MVC
    • Labels:
      None

      Description

      When using the view system, it is now possible to add arbitrary parameters. However it is currently possible to replace an existing one as BaseView::addParameters() uses + union operator and does not expose a setter.

        Issue Links

          Activity

          Show
          Jérôme Vieilledent added a comment - - edited PR: https://github.com/ezsystems/ezpublish-kernel/pull/1976 Related issue in EzCoreExtraBundle: https://github.com/lolautruche/EzCoreExtraBundle/issues/23
          Hide
          Bertrand Dunogier added a comment -
          Show
          Bertrand Dunogier added a comment - PR https://github.com/ezsystems/ezpublish-kernel/pull/1976 merged to 6.7, 6.9 and master.
          Hide
          Rui Silva (Inactive) added a comment -

          QA needs a practical use case scenario to test this.
          Can someone please provide one?
          Thank you.

          Show
          Rui Silva (Inactive) added a comment - QA needs a practical use case scenario to test this. Can someone please provide one? Thank you.
          Hide
          Bertrand Dunogier added a comment -

          [~rui.silva@ez.no] did you open the pull-requests ?

          Show
          Bertrand Dunogier added a comment - [~rui.silva@ez.no] did you open the pull-requests ?
          Hide
          Rui Silva (Inactive) added a comment -

          Bertrand Dunogier, yes, the PR did not include much more info that could be useful for QA tests though, than the description of this jira itself.
          As a matter of fact, we didn't quite understand the purpose of it:
          is it to test that we CAN actually replace an existing parameter or to add an arbitrary one, or both? The description seems clear "Cannot override view parameters" ( = can't replace), but it is referred "However it is currently possible to replace an existing one (...)" ( = can replace).
          However I did just read your latest comment on the PR, and seems somehow our doubts were justified
          And which simplest parameter configuration could one perhaps test this with?
          Thanks.

          Show
          Rui Silva (Inactive) added a comment - Bertrand Dunogier , yes, the PR did not include much more info that could be useful for QA tests though, than the description of this jira itself. As a matter of fact, we didn't quite understand the purpose of it: is it to test that we CAN actually replace an existing parameter or to add an arbitrary one, or both? The description seems clear "Cannot override view parameters" ( = can't replace), but it is referred "However it is currently possible to replace an existing one (...)" ( = can replace). However I did just read your latest comment on the PR, and seems somehow our doubts were justified And which simplest parameter configuration could one perhaps test this with? Thanks.

            People

            • Assignee:
              Unassigned
              Reporter:
              Jérôme Vieilledent
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: