Stack Exchange network consists of 183 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
Visit Stack Exchange
Stack Internal
Knowledge at work
Bring the best of human thought and AI automation together at your work.
Explore Stack InternalSounds nice, but I would prefer to have people responsible for committing code changes, not bots.
Besides, you want to make absolutely sure, that those changes do not break anything. We, forFor example, we have a rule that orders properties and methods alphabetically. This can have an impact on functionality, for example with the order of data and methods in WSDL files of WCF contratcscontracts.
Sounds nice, but I would prefer to have people responsible for committing code changes, not bots.
Besides, you want to make absolutely sure, that those changes do not break anything. We, for example, have a rule that orders properties and methods alphabetically. This can have an impact on functionality, for example with the order of data and methods in WSDL files of WCF contratcs.
Sounds nice, but I would prefer to have people responsible for committing code changes, not bots.
Besides, you want to make absolutely sure that those changes do not break anything. For example, we have a rule that orders properties and methods alphabetically. This can have an impact on functionality, for example with the order of data and methods in WSDL files of WCF contracts.
Sounds nice, but I would prefer to have people responsible for committing code changes, not bots.
Besides, you want to make absolutely sure, that those changes do not break anything. We, for example, have a rule that orders properties and methods alphabetically. This can have an impact on functionality, for example with the order of data and methods in WSDL files of WCF contratcs.
