Skip to content
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

Better Responses #11

Open
WinterBlox opened this issue Nov 5, 2023 · 0 comments
Open

Better Responses #11

WinterBlox opened this issue Nov 5, 2023 · 0 comments
Labels
Priority - Low Effects are mostly ignorable Type - Enhancement Optimization or Feature Request

Comments

@WinterBlox
Copy link
Owner

At the moment, the way you access server responses after they've been parsed into global.response is VERY hacky. For instance, lets say you did an auth request to the server for an account and then you want to get the message that the server sent back. You'd have to do: global.response.response.message

response.response? As you can see, it's more cluttered than it should be. The idea is to make a sub variable that stores what global.response stores now instead, and put the organized result in global.response instead.

@WinterBlox WinterBlox added Type - Enhancement Optimization or Feature Request Priority - Low Effects are mostly ignorable All Platforms 🌎 labels Nov 5, 2023
@WinterBlox WinterBlox added this to the FrostJolt v1.0.0 milestone Nov 5, 2023
@WinterBlox WinterBlox pinned this issue Nov 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority - Low Effects are mostly ignorable Type - Enhancement Optimization or Feature Request
Projects
None yet
Development

No branches or pull requests

1 participant