Jonathan Hedstrom
Jonathan Hedstrom
This looks great! Thanks for diving into that. I can merge the PR as it looks good to me.
Hmm, I can see that being problematic. Any code run natively (meaning not through a new bootstrap via the UI) will have the `REQUEST_TIME` from when the code is first...
We can explore adding a `ViewsContext` that just provides low level functionality, no step definitions...
Related: #487.
Makes sense to me!
There's a few options. If running in javascript, then you can go the verbose route, and say: ``` ... And I click "Menu Settings" And I fill field... ``` if...
Ah, I didn't realize those weren't links. Running in JS, the `And I click :link` I thought that worked with elements other than `a` but perhaps not... I'd certainly review...
Can you run with the `-v` option and post a stack trace? That might be helpful to pinpoint what is asking for the container so early on.
Line 2 up there appears to be the culprit: ``` features/bootstrap/FeatureContext.php(529): Drupal::entityQuery('user') ```
It should definitely be possible, but can depend on how your contexts are setup (for instance, is the `api` driver setup as Drupal in your `behat.yml`, etc)