You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 18, 2024. It is now read-only.
Won't this be solved when #160 is committed? Should we focus our attention there instead?
@damienmckenna, I agree that 160 will be an important step forward for this project but the current PR's that try to solve that are in (very) a bad shape.
Have a look at #570 (review) I moved over the initial branch from amitaibu:160-remove-complex-widget to this repository so we can work on it more easily. I noticed you created a merge branch for different PR's, any chance you could have the work spent there flow back to #570?
@MPParsley,
The PR I created (#571) was a stopgap I needed for a project to combine the three PRs so it could be added to a composer workflow.
I'll try to make time to work on #570 and the others to get them into a finished state that could be committed.
Won't this be solved when #160 is committed? Should we focus our attention there instead?
I have no idea. But if it does, it's still a question if it will be merged in time. That means before the support for Drupal 8.7.x is dropped. Then we can "won't fix" this. Otherwise this will get a simple cleanup PR.
Remove the
match_limit
schema fromfield.widget.settings.og_complex
when dropping support for Drupal 8.7.x.The text was updated successfully, but these errors were encountered: