Have been debugging for 4h why Hasura wouldn't accept the TMDB spec, I took a very round about approach to solving my issue as I got an error of Invalid spec: right-hand side of 'in' should be an object, got undefined
. In the end I decided to do some simple binary search with a json editor to find the offending path, in 20 minutes I found that the path movie/{movie_id}/changes
has no defined response schema object. Leading to that weird error. Why is this? Is there a specific reason or just an oversight? @TravisBell
I got Hasura to parse the schema by removing the content field on the 200 response object in the offending path. Needless to say, I screamed so loudly and ear raped my roommate once I got it working. I've had this issue back in March 2023, but I just got round to taking a look at the project again. Sorry roommate.
找不到电影或节目?登录并创建它吧。
robigan 的回复
于 2024 年 03 月 03 日 3:09下午
Btw, I used a custom script found in https://chat.openai.com/share/f0818c2d-ab1f-4ae1-b318-ae13306fb72e that removed the examples from all paths as it was causing some memory issues with the Hasura web portal.
Travis Bell 的回复
于 2024 年 03 月 04 日 12:03下午
Hi @robigan,
Are you using a current version of the OAS file that can be found here: https://developer.themoviedb.org/openapi ?
I ask because you mention a file from 2023. Since that time in 2023, we have migrated off the old API docs provider, so that file is completely different from what is currently generated.
robigan 的回复
于 2024 年 03 月 04 日 12:09下午
Yup, using the latest copy of the oas file found there. By 2023 I mean it was the week just after you had posted the new migrations.
Travis Bell 的回复
于 2024 年 03 月 04 日 12:14下午
Ok, got it.
Well, ya, ReadMe is the one generating those files so there's not much I can do. It's up to them to generate a valid spec.
robigan 的回复
于 2024 年 03 月 04 日 2:01下午
True, but the response body on the aforementioned route is empty. Even on the official tmdb api viewer. On your side does the response body to that route show up?
Travis Bell 的回复
于 2024 年 03 月 04 日 8:38下午
How's it look now?
There was an extra object (
{}
) defined at the beginning of the response that shouldn't have been there.