Bug: Auto-generated Upsert API endpoint to 'user' model is bugged with wrong underlying graphQL.
I'm trying to create an upsert call to the gadget API for the default 'user' object in the Web app template.
The API generated docs for an Upsert call, are in the first image. But when you actually try to run that in the playground (or make the call in your files) you get errors saying neither email not password have been provided (even though they have). As shown in image 2.
No idea what is going on here at all? Is the underlying graphql mutation broken?
5 Replies
This message can be ignored, as it is covered by a different thread (see below messages)
The plot thickens.... When i select the graphQL version of the gadget "USER" api. it gives me a mutatation which applies to a totally different model - pipedriveDeal. See screenshot. This API and its documentation seem very bugged
Even if you generate a new Web App tailwind template from scratch and try an upsert in the playground with the example given, the error persists. So it is an underlying problem with the upsert API generation.
Will take a look! I suspect that this is due to the User model having non standard actions and we aren’t accounting for that correctly
The documentation bug has been pointed out already, it doesn't load the correct code examples when clicking through the links in the sidebar, you have to reload the page
https://discord.com/channels/836317518595096598/1336696385701023855
Will have a try with a hard refresh now, see if that fixes the documentation issue, if not the underlying graphql issue
Yes it does. So the documentation issue can be ignored, it's just the javascript API client not recognising the email + password that is the still standing issue
Have solved it for myself by using the api.user.mutate() and the graphQL, in case anyone else is struggling with it.