I haven’t said it in a while, but I want to make sure everyone knows that I really appreciate what @eric and @john are doing at @phparch. I think the work they’re doing is awesome!
Once again it's Developer Appreciation Day - a thank you to everyone who has diligently contributed to the development of the #TYPO3 project over the past month. Cheers to you! 🧡
@supergarv Yup! It's a case I hadn't considered properly when I designed the system and I can't see any behaviour which would be 'correct'. I need to have a big rethink and do a 2.0 one day.
@joachim Hhm. How about having two interchangeable solutions then, or some kind of "bugfeature switch"? Would it be able to sort out by the users of the lib/app specifying what they would intent/expect? Sounds interesting! 🧐
In PHP, we have classes with methods inside them. Would making all your methods public be a good idea? No, because some of them should be used only by the class they're in and not anywhere else. What about class constants?
TYPO3 is supercharging newsrooms and publishing houses!
We’ve published a new industry vertical landing page for the News, Media, and Publishing sector, full of information on TYPO3’s features can ensure companies can deliver content to their audiences quickly and securely.
Find out how news and media companies can make the most out #TYPO3.
@nyamsprod as other have said, definitely a BC for A due to class removal. And due to the inverse relation, you don't even have an easy migration path (like with a plain class_alias or an extension)... 😔
@alessandrolai I have an easy way out I can bump package A to the next major and keep B in it's current version and move the class there effectively embracing the BC break BUT it makes my monorepo ugly to work with until I bump package B to the same version as package A and I need in the meantime fin a good git-split tool able to handle 2 majors release ... that's the complex part
@alessandrolai@Girgias If there is I haven't found it, yet. @Girgias suggested rule sense like where it belongs. What I meant to say is THAT RULE doesn't seem to care what order readonly comes.
If you haven't picked up a free copy of my book, Mastering Object-Oriented PHP, make sure you head over to https://masteringobjectorientedphp.com and get your copy today! Free is my way of giving back to the PHP community.