-
Notifications
You must be signed in to change notification settings - Fork 151
Large refactoring (ideas for v3?) #150
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Docblock changes. Reorder methods to be logical.
Update README.md.
Changing all the styling makes this basically unreviewable, sorry. And things like factories are questionable at best. Are there any actually interesting changes in this PR that could be split into separate pr? |
Would you be open to bringing in cs-fixer as a start, with smaller commits? Adopting a known coding standard here will help with future contributions. One of the changes here, is the splitting up of Source / GoldSource logic, see: This also includes the RCON code, now nicely interfaced: Hidden in this PR are also changes to decouple the main SourceQuery class from the RCON code, we now pass in an instance of RconInterface via the constructor (this is why the factory was created, to ensure we are creating valid combinations of SourceQuery + Socket + Rcon). Also hidden - we no longer pass around $engine - we simply use Socket::getType. If you would prefer to not continue with any of the above changes, we can close this off, with work continuing on the fork. |
Yeah unfortunately I'm not seeing any changes here that aren't just simply a refactor. You are of course free to keep this as your own fork. The breaking changes caused by the refactor are not really worth it, imo. |
While building a tool for local server status listing and debugging - what started out as a minor code audit, turned into a refactor.
Lots of commits here, so maybe not merge-able - but there's a few things here which could be useful for the future (v3?).
Changes:
Breaking Changes: