Feeling Lucky
?
[#38744] - multiple in plugin fields list with api
- Closed
- 13 Sep 2022
- Medium
- Build: 4.2-dev
- # 38744
- Diff
- antonbag:4.2-dev
User tests: Successful: Unsuccessful:
Pull Request for Issue # .
Summary of Changes
Array of values from plugin fields list with multiple option active
Testing Instructions
Described in issue #38745
Actual result BEFORE applying this Pull Request
"mylistfield": []
Expected result AFTER applying this Pull Request
"mylistfield": [
{
"value": "Value 1",
"alias": "value-1"
},
{
"value": "Value 2",
"alias": "value-2"
},
],
Documentation Changes Required
| Status | New | ⇒ | Pending |
joomla-cms-bot
- | Category | ⇒ | Front End Plugins |
| Labels |
Added:
?
|
||
| Status | Pending | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2022-09-13 12:23:22 |
| Closed_By | ⇒ | wilsonge |
wilsonge
- comment
- 13 Sep 2022
This is already contained in the following PR https://github.com/joomla/joomla-cms/pull/38655/files which handles more fields with the same issue - so I'm going to close this PR in favour of the more complete one linked.
Thankyou however for contributing this to the project - it is very appreciated!
antonbag
- comment
- 13 Sep 2022
Thank you!!! @richard67 and @wilsonge :)
@antonbag Please update the "Pull Request for Issue # ." at the top of the description of this pull request (PR) to "Pull Request for Issue #38745 ." so it is clear that this PR solves that issue. Thanks in advance.
In general, if you find an issue and have already the solution for it, it is enough to create a PR. There is no need to create an issue in addition. When we have a PR to solve an issue, we close the issue here.