Harings Rob

Thinking a bit about menu's in general. Now that we have packages that register menu items as well (but without control). It could be interesting to also make this a...

Closing this to be reimplemented (which will be easier) in 3.x (using alpinejs)

https://github.com/rectorphp/rector/blob/62e856362bcb2f407f0c27ae1529cc8da531e65c/docs/rector_rules_overview.md AddPropertyTypeDeclarationRector AddReturnTypeDeclarationBasedOnParentClassMethodRector ----------------- A better strategy would be to look at the parent, and fix it based on that. Usable: MakeInheritedMethodVisibilitySameAsParentRector AddParamBasedOnParentClassMethodRector AddPropertyTypeDeclarationRector AddReturnTypeDeclarationBasedOnParentClassMethodRector ParamTypeByParentCallTypeRector ParamTypeDeclarationRector ChangeMethodVisibilityRector

Hey @sineld, could you provide some steps to reproduce? Then I can write tests for this.

Hey @antonioribeiro, I was checking this, but I feel that I cannot find a use case for this. A browser can refer to an external entity. But that can be...

~~When you set `'use_property_fallback' => true,` in you `translatable.php` it should work without changes.~~ Nevermind, not related

Hey @broakenmedia, Can you give this another go on 2.8? I tried to reproduce but this seems to work fine.

Hey @ifox, shouldnt the slug update instead of creating a new entry? This is the db after entry create + update. Asking because there might be a reason for it.

Hey @ConstantMath, First of all, thank you for your contribution! I was checking this, but it is missing the replication of model translations, blocks, and repeaters. And at the same...

No worries at all @ConstantMath, the pr is a very good starting point. Maybe an alternative idea could be that if a model is not revisional we introduce a new...