I second that!
Context is key here. There are objects in our daily life that are just a way to organise data. DTO's, entities and such. The integrity of those objects should be made sure from the outside anyway.
And then there are objects whose inner state is critical. It's objects where you might only want to expose properties via constructor and getters to control the state.
However, both types don't really justify hiding protected or private properties behind getters and setter that don't do anything else but to expose said properties as if they were public in the first place.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.