Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.In #1774312: Create.js: yay or nay *and*: when?, there was much discussion and broad support for basing inplace editing on VIE and Create.js.
#1824500: In-place editing for Fields has been submitted to the core queue. As we've done with other vendor libraries, I propose we commit these separately in this issue to make patch uploads in that issue smaller and easier to review. Here is just that portion.
Some important notes about the state of these libraries
From #1824500-9: In-place editing for Fields:
We're still working with @bergie to improve Create.js in some areas, that will allow our code to be slightly simplified further/made more consistent. We're also going to work with him to make the builds smaller, but that can definitely be a post-feature freeze thing. After talking to @nod_, the current size is definitely small enough [14KB for VIE+Create, minified and gzipped]... We include the unminified builds of Create and VIE for now, for easier debugging.
From #1824500-26: In-place editing for Fields:
[This] patch includes the VIE.js "core" build and Create.js "editonly" build. I've indicated this as such in the library definitions, but honestly, this may imply that it's not a perfect fit to have these non-complete builds in core/misc, exactly because they're incomplete. That being said, it should be possible to add complementary builds for both that when combined would be equal to the complete build. That will need some upstream work though.
| Comment | File | Size | Author |
|---|---|---|---|
| #9 | 1849526-vie_create_upstream_fixes-9.patch | 11.8 KB | Wim Leers |
| create.js_.patch | 187.22 KB | effulgentsia | |
Comments
Comment #2
effulgentsia CreditAttribution: effulgentsia commentedcreate.js_.patch queued for re-testing.
Comment #3
sunThanks! Makes sense.
Other issues of this kind are typically assigned to @Dries to sign off, so let's do the same here.
Comment #4
Wim LeersNote that according to #1824500-30: In-place editing for Fields, @nod_ (D8 JS maintainer) is in favor of Create.js and VIE.js. I'll ask him to comment here.
Comment #5
nod_Yep a big fat +1 from me, see the review linked to above and more importantly the edit code before createjs/VIE was used to really get how much we'd want them :)
Comment #6
webchickThis is a blocker for a feature, so it doesn't make sense to block other features on it. :)
Comment #7
Dries CreditAttribution: Dries commentedThis makes sense, and was discussed in other forums too. I'm comfortable with committing this once we are below threshold.
Comment #8
webchickOk, we're not quite below thresholds, but it's pretty damn close (101 majors, 18 criticals of which 4 are change notices), and I'd like to make sure we get some features committed this week. :) Therefore...
Committed and pushed to 8.x. Thanks!
Comment #9
Wim LeersI hope this is the right way to get upstream fixes for 3rd party libs committed. I apologize if it is not.
Comment #10
webchickHm. Looks like this is a straight-up update of the VIE/Create.js code based on upstream improvements, so committed / pushed to 8.x.
I think in the future, we should get a different issue for this though, ala #1834594: Update dependencies (Symfony and Twig) follow up fixes for Composer, because my guess is this is going to happen A LOT. :)
Comment #11
Wim LeersThanks for the commit, especially thanks for the sample issue, now I know what the recommended way to do this is :)
Comment #12.0
(not verified) CreditAttribution: commentedMinor edits