Closed (fixed)
Project:
Drupal core
Version:
8.0.x-dev
Component:
entity system
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
1 Dec 2015 at 13:50 UTC
Updated:
18 Feb 2016 at 01:44 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
dawehnerThere we go.
Comment #3
webflo commentedComment #4
webflo commentedComment #5
dawehnerThere we go, with a test.
Comment #6
dawehnerThere we go.
Comment #8
berdiras discussed, I think we should document here that this is basically already deprecated and will be removed in 9.x, it's just here for BC.
Before we'd do that, I'd actually talk to @catch about this, maybe he thinks that we don't need this and can just switch?
Comment #9
dawehnerUpdated the docs a bit for that point. Its hard to describe that the deprecated value is the default for now.
Comment #10
catchYeah what happens if we just remove the static cache?
Comment #11
dawehnerYeah this is the question ... could this break contrib / custom code out there?
Comment #12
slashrsm commentedLet's see what testbot says about this. I will give no info about the contrib/custom, but it is a start.
There might be contrib/custom code that relies on form object always being the same. But I am thinking if that's abusing details of internal implementation? Documentation for getFormObject() says "Creates a new form instance". Not a word about persisting form object after it was initially created.
Comment #13
slashrsm commentedDiscussed this with @catch on IRC. He suggested to commit to 8.1.x immediately and leave RTBC for a while for 8.0.x to test it a bit more.
Comment #14
slashrsm commentedAdded Change record draft.
Comment #15
berdirI agree, I don't think it's an API that we statically cache there. The documentation even explicitly says new.
Lets get this into 8.1.x as suggested by @catch.
Comment #18
catchLooks like alexpott just committed this.
Comment #19
slashrsm commentedChange record published.
Comment #21
catchCherry-picked to 8.0.x, thanks!