- All
*Includeenums are now chainable so doingListNodesQueryInclude.SERVERS + ListServersQueryInclude.USERreturnsservers.user
Also now instead of<enum>.toQueryString(...)(likeListServersQueryInclude.toQueryString(...)) i dolistOf(...).toQueryString() - Used the new include enum chaining in 2 places:
- node servers tab: it now makes way less HTTP requests since the user, nest & egg are directly returned with the server, saving me from making multiple HTTP requests to fetch all users, nests & eggs (which would’ve taken a long time on a large server that for example has thousands of users, since it was fetching at a rate of 50 users per HTTP request, and it being a mobile app, internet might not be fast too)
- servers screen, now it fetches the egg variable together with the nest instead of having to fetch the egg’s data
- Moved
ApiErrorResponsein amodelsfolder for better organization
this is a code only change so ig i’ll show pics of the code
Comments 0
No comments yet. Be the first!
Sign in to join the conversation.