Luke Towers

@arvislacis could be there was a commit that was tagged as 1.15.1 and your first update got it (the "unstable" composer.lock) and then reverting your lock file to the old...

It's also not documented behaviour AFAIK, and it should at least be configurable.

Yeah, I'm pretty flexible about what it would be called, @jaxwilko was working on making Winter work on Laravel Vapor and as part of their deployment process they copy everything...

The correct way to handle this is by passing the readOnly property to the `relationRender` method. Something like this in your partial that renders the relation controller: ```php ``` should...

Are you using a custom toolbar partial or are you using toolbarButtons? https://github.com/wintercms/winter/blob/develop/modules/backend/behaviors/RelationController.php#L598-L600 should be preventing the buttons from showing up. If it's not, then it's possible that the relation...

Try ```php ```

@AIC-BV I think the solution we actually need is to make the previewMode variable accessible to the partial. Currently, `type: partial` fields have no access to the underlying Form widget,...

Could we explore having the fields being managed by an embedded Form widget to bring the full power & flexibility of that to the inspector? Currently only a very limited...

Thanks for the feedback! > Did you have any thoughts on what to do about the winter.user.getNotificationVars event? Yeah, we'll leave it as it, it's just an event that ties...

> although I am a bit worried that the feature my boss expected to be available this week may not be out for an extended period of time @josephcrowell You...