Added large ints test case

[nesitor]

Fix: Add a test for large ints to ensure don't raises a TypeError

Self proofreading checklist

• Is my code clear enough and well documented
• Are my files well typed
• Are there enough tests

Changes

Added a test case ensuring that large ints doesn't break the json load and dump

How to test

Execute the test suite

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 94.38%. Comparing base (7334301) to head (b5fcbbf).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #611   +/-   ##
=======================================
  Coverage   94.37%   94.38%           
=======================================
  Files          91       91           
  Lines        4910     4916    +6     
  Branches      677      677           
=======================================
+ Hits         4634     4640    +6     
  Misses        241      241           
  Partials       35       35           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Forgot about JS

[hoh]

What strategy should be used to avoid breaking Javascript and non-Python clients ?

Javascript integers are limited to about 2^53

There are already have a few messages stored in the database with too large integers, and loading these from JSON in any language other than Python would result in a client crash if these are served.

Would it make more sense to handle this problem on the server side and not serve these messages ?
(as well as not accepting new ones)

[nesitor]

What strategy should be used to avoid breaking Javascript and non-Python clients ?

Javascript integers are limited to about 2^53

There are already have a few messages stored in the database with too large integers, and loading these from JSON in any language other than Python would result in a client crash if these are served.

Would it make more sense to handle this problem on the server side and not serve these messages ? (as well as not accepting new ones)

At the moment Javascript don't crash handling this messages with large ints, the unique thing that does is loose precision (see https://stackoverflow.com/questions/34561827/how-do-i-deal-with-number-greater-than-253-in-javascript#:~:text=The%20%C2%B1253%20range,use%20a%20Javascript%20bignum%20library.). And the unique clients that we have for the API is JavaScript and Python.
I think that the API should not assume the task to check if the ints are so large or not, only if it can handle it and store it and not crash. The responsability about what is saved and what is loaded is from the user that saves the message, so if the API can manage, save and serve it without crash it is fine.