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

Server responses should adhere to same data type locally and online #20

Open
Andrej123 opened this issue Jan 24, 2017 · 3 comments
Open
Labels

Comments

@Andrej123
Copy link

There's a discrepancy between server responses weather it's run locally (discrepancy spotted on macOS 10.12.2 Sierra) vs. the server that's running online (clocker.goranche.net).

Sample for local response for getClients:
[{ "id": "1", "name": "AndCli" }, { "id": "2", "name": "And2Cli" }, { "id": "3", "name": "And3Cli" }, { "id": "4", "name": "Andrej" }, { "id": "5", "name": "And" }]

Sample for online response for getClients:
[{ "id": 1, "name": "Someone who pays me" }, { "id": 2, "name": "Sponsor" }, { "id": 3, "name": "Andrej" }]

@Andrej123 Andrej123 added the bug label Jan 24, 2017
@goranche
Copy link
Member

🤔 it might be easier (and cleaner?) to handle this in the client...

@Andrej123
Copy link
Author

Yeah, I definitely agree that it might be easier. I'm not interested in "easier". I'd like to learn something new. I agree that it might be cleaner, and that's one thing I'll keep in mind.

I'd like to at least give it a try to solve the issue on the server side. If I won't be able to progress fast enough, or the solution would be indeed be coming out messy I'll opt for the client side solution.

@goranche
Copy link
Member

👍 knock yourself out...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants