Banana Cake Pop IDE length query issue

[olu-lebara]

I use Banana Cake Pop IDE in my project (.net 7 ASP.API) for a long time with no issues. But recently I've found very strange behavior - if request is too long, IDE will send to API back-end previous request, ignoring current query (in my case it's mutation) which is in IDE reflected. Don't know concrete max length, but the reason is in length for sure. Once I'll make query shorten - IDE will send updated one. I use HotChocolate.AspNetCore 11.3.8 version.

If use the same query thru Postman - no issue. Mutation with issue has more 5.4K symbols. With length about 4K - no issue. Expected solution is to have an error about long query, or do not have such limitation at all (like in Postman). Current behavior causes to bad issues, as far as IDE just sends previous query one more time with no specific warning or error.

PS: Question is duplicated from stackoverflow - https://stackoverflow.com/questions/78472543/banana-cake-pop-ide-length-query-issue

[olu-lebara]

"Request Body" in IDE (tab in bottom right corner) shows JSON request that was sent (previous one), not the long one from query editing box

[olu-lebara]

Could be it has matter, the structure of mutation request if follow:

mutation { addItem (input: {
itemDetail1: 1234,
itemDetail2: "5678",
itemDetails3: [
{subitemDetail1:1,subitemDetail2:false,subitemDetail3:true},
{subitemDetail1:2,subitemDetail2:false,subitemDetail3:true},
{subitemDetail1:3,subitemDetail2:false,subitemDetail3:true},
...
{subitemDetail1:100,subitemDetail2:false,subitemDetail3:true}]
}) {
status
failMessage}}

I have quite huge amount of subitemDetails, that's why overall mutation query is very long.