We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi all! The response of the different endpoints are not homogeneous, I give an example.
https://api.genshin.dev/artifacts -> ["adventurer","archaic-petra",...] ✅ https://api.genshin.dev/characters -> ["albedo","aloy","amber",...] ✅ https://api.genshin.dev/characters/aloy -> {"name":"Aloy","title":"Savior From Another World",... ✅ https://api.genshin.dev/consumables -> ["food","potions"] ✅
https://api.genshin.dev/consumables/food -> {"pile-em-up":{"name":""Pile 'Em Up"",... ❌ I think it should be like this https://api.genshin.dev/consumables/food -> ["pile-em-up","adeptus-temptation","adventurers-breakfast-sandwich",...] ✅
I understand the reason why you have created it this way, but this complicates the API and this request optimization must be done in front
Is it possible to unify the response data structure?
Thx so much!
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi all!
The response of the different endpoints are not homogeneous, I give an example.
https://api.genshin.dev/artifacts -> ["adventurer","archaic-petra",...] ✅
https://api.genshin.dev/characters -> ["albedo","aloy","amber",...] ✅
https://api.genshin.dev/characters/aloy -> {"name":"Aloy","title":"Savior From Another World",... ✅
https://api.genshin.dev/consumables -> ["food","potions"] ✅
https://api.genshin.dev/consumables/food -> {"pile-em-up":{"name":""Pile 'Em Up"",... ❌
I think it should be like this
https://api.genshin.dev/consumables/food -> ["pile-em-up","adeptus-temptation","adventurers-breakfast-sandwich",...] ✅
I understand the reason why you have created it this way,
but this complicates the API and this request optimization must be done in front
Is it possible to unify the response data structure?
Thx so much!
The text was updated successfully, but these errors were encountered: