generateNftTokenId - NftSignature 'v' entry returns an int, not string per spec

[bobwith2bees]

Hi there,

The generate_token_id API is returning an int for the signature "v" field, when the spec specifies it should be a string (in quotes).

This is throwing off my json deserializer. I am using the OpenAPI code generator, so I can tweak the spec to be an int, but wanted guidance on whether that was a good idea or not.

Spec - https://api-reference.rarible.com/#operation/generateNftTokenId
v required | string 
yaml:
NftSignature: required: - "r" - "s" - "v" type: "object" properties: v: type: "string" format: "byte" ...

Postman Request:
ethereum-api-staging.rarible.org/v0.1/nft/collections/:collection/generate_token_id?minter=0x72A4408DA42DE870499c1841D0e4a49f864e34ba

Postman Response:

{
    "tokenId": "51853873187524799243313032258623492611584136611923237689466576623960428904452",
    "signature": {
        "v": 28,
        "r": "0xe77b3fac57f71600d5f5017a3ff99f5ec00c32d4c3910078c2cc4af1be18acd6",
        "s": "0x77b647c58d87f59b3bc8fcb25c96861f79cc35dd475dc9f91ee75ee2a9eee259"
    }
}

Final Dart/Flutter error in case it helps others find this issue: Deserializing '27' to 'String' failed due to: type 'int' is not a subtype of type 'String' in type cast

[evgenynacu]

@bobwith2bees thanks
fixed, now it's a number in apidoc too