-
Notifications
You must be signed in to change notification settings - Fork 8
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
Complete WorldState.Data models for the worldstate parser. #11
Comments
Alerts should be done, created |
Because the data is pretty different between each route |
Ah alright, well that's not too bad. |
I've been pulling as many common fields into the base object, but it's pretty varied. I need to go through and clean up some of the responses like for Twitter. At some point, I'd like to write it in bicubic routes similar to what Nexus stats uses for their API that makes their docs largely auto-generated. |
It's not a big problem, I'm just surprised DE didn't think about making their API cleaner in the first place. |
Unable to do events for now since the docs say |
You can see the possible fields on the js repo in wfcd/warframe-worldstate-parser |
I'll also make an interface for cycles. |
Sorties are done. |
oh, i have actual swagger docs now: swagger |
this codegen might make it go a bit faster. |
All of these models are returned by the worldstate api at api.warframestat.us, so we'll need to make C# models for every item returned to be used when deserializing from the JSON results.
If I missed anything please let me know.
The text was updated successfully, but these errors were encountered: