Handling "either or" field arguments in application schema GraphQL query

[cafca]

According to our specification, the id and viewId field arguments are strictly "either or" and an error should be returned if both are given. Aquadoggo currently ignores the document id in this case.

We should either adapt the aquadoggo implementation or change the spec.

[adzialocha]

As far as I know the tasks currently panic if they detect invalid task arguments. I've tried to find an either/or way to do types in Rust but couldn't find anything native, do you have an idea?

[cafca]

Oh, this is just about field arguments in the GraphQL api.

Wouldn't an enum work for tasks though?

[adzialocha]

Oh, this is just about field arguments in the GraphQL api.

Oh lol, sorry, I've updated the issue title 👍

Wouldn't an enum work for tasks though?

Yeah, good point! I'm sure I've tried something and it didn't work out because of something else .. but worth another shot!

[adzialocha]

https://www.youtube.com/watch?v=1PSVZGfhjWk

[cafca]

https://youtu.be/1PSVZGfhjWk?t=2035 ............ ???????

[adzialocha]

From last meeting: We decided that it should be fine if they are both set, the node will go for the viewId then