- Issue created by @Grimreaper
- Assigned to Christian.wiedemann
- 🇩🇪Germany Christian.wiedemann
1. This is done wrong in Block Source which we propably remove.
2. I am not sure about that. Actually I think it is good to have allways the same key in every consumer. We may provide a getConfigurationKey() function to overwrite that? Should we? @pdureau @Grimreaper
3. Should we provide an own trait for that? I would vote for that- @pdureau @Grimreaper - Status changed to Needs work
4 months ago 5:44pm 21 July 2024 - Assigned to Grimreaper
- Status changed to Postponed: needs info
4 months ago 11:03pm 21 July 2024 - 🇫🇷France pdureau Paris
This is done wrong in Block Source which we propably remove.
We have an issue about that: 🐛 [2.0.0-beta1] Blocks implementing PluginFormInterface don't work with BlockSource Needs review
We will not remove BlockSource but introduce a whitelist.2. I am not sure about that. Actually I think it is good to have allways the same key in every consumer. We may provide a getConfigurationKey() function to overwrite that? Should we? @pdureau @Grimreaper
3. Should we provide an own trait for that? I would vote for that- @pdureau @GrimreaperNo opinion. I assign to @Grimreaper
- Merge request !150Issue #3444770 by Grimreaper: [2.0.0-beta1] ComponentFormBuilder: make it more dynamic. POC → (Open) created by Grimreaper
- Issue was unassigned.
- Status changed to Needs work
4 months ago 7:36pm 22 July 2024 - 🇫🇷France Grimreaper France 🇫🇷
Hi,
1. Now that BlockForm return $form that is passed to it, no problem.
2. I opened a MR with a POC of what I had in mind and with current codebase. I have just edited the files, not tested. This can be used to discuss.
3. Vote for a new trait too. - Assigned to Christian.wiedemann
- 🇩🇪Germany Christian.wiedemann
@Grimreaper I tested your code and add the configuration_id to all places. From my point of view it should work now. (But we realy need e2e tests now)
- Status changed to Needs review
4 months ago 5:05pm 28 July 2024 - Assigned to Grimreaper
- Assigned to Christian.wiedemann
- Status changed to Needs work
4 months ago 7:39am 30 July 2024 - 🇫🇷France Grimreaper France 🇫🇷
@Christian.wiedemann,
Thanks for the update.
I put some code review comments.
Also point 3, creating a new trait remains to be done.
- 🇩🇪Germany Christian.wiedemann
@Grimreaper I updated/fixed your comments. We decided to no implement an own trait for rendering because they belong somehow together. Thanks!
- Status changed to Needs review
3 months ago 10:17am 4 August 2024 - Assigned to Grimreaper
- Assigned to Christian.wiedemann
- 🇫🇷France Grimreaper France 🇫🇷
Hi,
@Christian.wiedemann, thanks for your work. Ok for me now.
I have rebased and removed the todo.
You can give a last review in case my rebase broke stuff.
- Merge request !180Resolve #3444770 "2.0.0 beta1 componentformbuilder make merge" → (Merged) created by Christian.wiedemann
- 🇩🇪Germany Christian.wiedemann
Rebase was the hell. So I created a merge branch and opened a pull request. I tested Views Layouts and Field formatters. We should merge it.
https://git.drupalcode.org/issue/ui_patterns-3444770/-/tree/3444770-2.0....
- Status changed to Needs work
3 months ago 8:08am 11 August 2024 - 🇫🇷France pdureau Paris
Hi Christian,
So I created a merge branch and opened a pull request.
So, this one? https://git.drupalcode.org/project/ui_patterns/-/merge_requests/180
I am not very comfortable about opening a new branch, instead of doing the rebase. I guess rebase was hell because it was done late. So, I will ash @grimreaper to have a look, because I don't feel competent enough in this subject.
However, before that, it seems phpstan check has failed: https://git.drupalcode.org/project/ui_patterns/-/jobs/2407677
Line src/Form/ComponentFormBuilderTrait.php (in context of class Drupal\ui_patterns_field_formatters\Plugin\Field\FieldFormatter\ComponentFormatterBase) 121 Method Drupal\ui_patterns_field_formatters\Plugin\Field\FieldFormatter\ComponentFormatterBase::getComponentConfiguration() invoked with 1 parameter, 0 required. 159 Method Drupal\ui_patterns_field_formatters\Plugin\Field\FieldFormatter\ComponentFormatterBase::getComponentConfiguration() invoked with 1 parameter, 0 required. 192 Method Drupal\ui_patterns_field_formatters\Plugin\Field\FieldFormatter\ComponentFormatterBase::getComponentConfiguration() invoked with 1 parameter, 0 required. Line src/Form/ComponentFormBuilderTrait.php (in context of class Drupal\ui_patterns_views\Plugin\views\row\ComponentRow) 121 Method Drupal\ui_patterns_views\Plugin\views\row\ComponentRow::getComponentConfiguration() invoked with 1 parameter, 0 required. 159 Method Drupal\ui_patterns_views\Plugin\views\row\ComponentRow::getComponentConfiguration() invoked with 1 parameter, 0 required. 192 Method Drupal\ui_patterns_views\Plugin\views\row\ComponentRow::getComponentConfiguration() invoked with 1 parameter, 0 required. Line src/Form/ComponentFormBuilderTrait.php (in context of class Drupal\ui_patterns_views\Plugin\views\style\ComponentStyle) 121 Method Drupal\ui_patterns_views\Plugin\views\style\ComponentStyle::getComponentConfiguration() invoked with 1 parameter, 0 required. 159 Method Drupal\ui_patterns_views\Plugin\views\style\ComponentStyle::getComponentConfiguration() invoked with 1 parameter, 0 required. 192 Method Drupal\ui_patterns_views\Plugin\views\style\ComponentStyle::getComponentConfiguration() invoked with 1 parameter, 0 required.
Can you run the checks locally before pushing?
Also, there is one commit more to rebase from 2.0.x
- Status changed to Needs review
2 months ago 7:27pm 5 September 2024 - 🇩🇪Germany Christian.wiedemann
I rebased to the latest 2.0.x. Check the merge branch.
- Assigned to Grimreaper
-
grimreaper →
committed 66fb5737 on 2.0.x authored by
christian.wiedemann →
Issue #3444770 by christian.wiedemann, grimreaper, pdureau: [2.0.0-beta2...
-
grimreaper →
committed 66fb5737 on 2.0.x authored by
christian.wiedemann →
- Issue was unassigned.
- Status changed to Fixed
2 months ago 9:24am 6 September 2024 - Status changed to Fixed
2 months ago 7:27pm 15 September 2024