-
Notifications
You must be signed in to change notification settings - Fork 24
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
Update to new .getCategory #247
Conversation
Note comment in issue #246 (comment) |
I've also been running with the same set of changes as this PR, with the additional change to the reference in I haven't had any issues since, no errors, or stream stopping (I left only the |
If the reference in |
Sorry for the confusion, all I meant by that anecdote was more the other unit known case and that seems good But in the group case I haven't checked the behavior/ what it should be and would be guesswork on my part to change without verification/cause so pointed it out but haven't acted on it Apologies for the anecdote; its more that it's not impacting me doesn't mean it's not a problem |
No need to apologise, I added my comment as more of a question to see if it is only units that are affected by the change to [EDIT/UPDATE]: group:getCategory() should work as before without needing any change. Source: ED Discord |
Uncertain of other impacts, the changes in this PR have allowed OverlordBot to function without issue, which is my only application using DCS-gRPC. My understanding was only Object was returning incorrect data prior to the change ED made in latest OB. |
Can you rebase this on to the current main branch which should fix lint failures. Also add an entry to CHANGELOG.md |
There is also the reference mentioned by @martinco on L25 of controllers.lua. Should that be included in this PR? |
- Fix for DCS API change to getCategory()
Not needed in this case. |
Update the code to be compatible with the new
.getCategory()
implementation which ED changed in the latest release.