List: remove item with drop with specified value" method

Created on 4 January 2023, almost 2 years ago
Updated 29 January 2023, almost 2 years ago

I'm working for the first time at this AMAZING system. Great job guys!!
This module is great after the big (big) Rules problems.

Problem/Motivation

I have simply to use "List: remove item" from multivalue field to remove a particular item.
With Drop first, last and index methods it works well, I have not result with "drop with specified value" method.

Steps to reproduce

Rule

Action

Field list

Feature request
Status

Fixed

Version

1.2

Component

Code

Created by

🇮🇹Italy ConradFlashback

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • Assigned to mxh
  • 🇩🇪Germany mxh Offenburg

    Will have a look at this.

  • @mxh opened merge request.
  • Issue was unassigned.
  • Status changed to Needs review almost 2 years ago
  • 🇩🇪Germany mxh Offenburg

    Added a block in the implementation for "List: remove item" that is supposed to work when choosing "drop by specified value" on a field item list, using a scalar value (string / number etc.).

  • 🇩🇪Germany jurgenhaas Gottmadingen

    Amazing, that's exactly the approach I had in mind when seeing this problem. Well done, thanks.

  • Status changed to RTBC almost 2 years ago
  • 🇩🇪Germany jurgenhaas Gottmadingen

    Merged into 1.2.x - wondering if this is a bug rather than a feature and should be back ported?

  • 🇩🇪Germany mxh Offenburg

    It's an improvement by directly supporting a field's item list, therefore I don't see it as a bug fix.

  • Status changed to Fixed almost 2 years ago
  • 🇩🇪Germany jurgenhaas Gottmadingen

    directly supporting a field's item list

    Well, we never mentioned that this was NOT supported in the first place. The expectation was that this was this original behaviour.

    However, I'm OK marking this as fixed without back porting it. For someone really relying on this, they can apply the patch into ECA 1.1 and make it work for them earlier.

  • Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.71.5 2024