Alessandro Desantis

@apotonick any chance you could jot down your thoughts on this?

@apotonick well, I guess generic schema definitions could benefit from it as well, but the use case I have is `:writeable`. Not sure where we'd want to do this exactly.

Hey @skywinder, are you still looking for help? We use this project [pretty extensively](https://github.com/solidusio/solidus_dev_support#changelog-generator) in the Solidus ecosystem for managing the changelogs of all our extensions, and we'd love to...

I agree, it's probably better to switch to standard and stop worrying about coding style altogether rather than trying to come up with our own rules for every situation. As...

If GitHub helps us make that transition smooth, I'm all in favor of this.

This seems to happen even when not touching the firstname/lastname attributes, even if you just click on "Update" in the Solidus backend.

@softr8 any chance you could split the improvements into multiple commits? It would make the Git history much more useful! 🙏

@tmtrademarked 👋 Unfortunately, I don't think there's a good way to do what you're asking right now (other than removing all the routes from solidus_api with some hack that leverages...

Got it, I think that makes sense too and we shouldn't have any issues implementing in a backwards-compatible manner, since the setting would be `false` by default. Can't promise anything...

I agree. Thinking about this at a higher level, our goal should be to make each gem completely independent of the others (other than solidus_core).