Alexander Lisachenko

@samsonasik Should we fork back again to the goaop org then to depend on own dependencies? At least it will be easier to maintain then

Here we go https://github.com/goaop/dissect, let me adjust this fork for our needs...

Granted you admin rights on https://github.com/goaop/dissect, dependency can be temporary used as `"goaop/dissect": "^3.0-dev"`

I can't push directly to your branch to contribute on this PR, check my commits here https://github.com/goaop/framework/compare/samsonasik-patch-1%7E3...samsonasik-patch-1 or cherry-pick what is needed

It slowly starts to work again! 🚀 Kudos!

> I can't push directly to your branch to contribute on this PR, check my commits here [samsonasik-patch-1~3...samsonasik-patch-1](https://github.com/goaop/framework/compare/samsonasik-patch-1~3...samsonasik-patch-1) or cherry-pick what is needed Definitely need to pick fixes for Serializable...

From the demos folder (can be opened in built-in server) almost everything works! 🚀 🕺 Still issues with some parts (sorry, code coverage is not full) - should we look...

> Yes, I think separate PR is better 👍 Ok, good, then let me work then in the evening today (need to go now), I would like to give some...

> just let me know what step by step to run the demo It is very easy, just follow https://github.com/goaop/framework?tab=readme-ov-file#step-0-optional-try-demo-examples-in-the-framework (but you can also just simply run the built-in PHP...

`goaop/dissect` part is ready - package is published, CI tool configured, cleaned a little bit with rector. Marked as major release 3.0.0 because we are bumping PHP requirement >=8.2