Alex Orosciuc
Alex Orosciuc
@LukeTowers just to better understand the status of this - no fixes are planned in the foreseeable future? Even if the case, why closing?
> Just some thoughts on this if anyone (or myself) wish to take this on: > > * Conventionally, a deletion action in most version systems is considered a "version"...
A minor UX improvement for which I have an implementation is showing an empty repeater form automatically if there are no existing repeater items yet. This helps avoid an extra...
> It's not Winter's responsibility to care about what proxies are doing to the response. An application doesn't operate in a vacuum, there are 3rd parties and they all rely...
@mjauvin I'm sorry I wasn't clear enough about what I would like to see as a feature in Winter CMS. You are right about the existence of `forceDelete()`, which I...
> Am I missing something here? `FormController's` implementation of deletion is a bit longer and I'm afraid developers risk breaking compatibility with it unless they duplicate `update_onDelete()` and add own...
> @lex0r you could always use a trait to add it to multiple controllers Well yes, just that it becomes a little clumsy because I will have to override two...
I thought would be nice for `FormController` to become aware of soft-delete models. They are not uncommon after all.
As a workaround and maybe source of inspiration for a proper fix something like below can be used: ```php class MyZip extends Zip { public const DEST_EXISTS_OR_UNWRITABLE = 101; public...