You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In researching qdrant/qdrant-web-ui#87, this library is where we lose the point ID precision because of the JSON.parse call not supporting big integers. I'm not aware of a way to solve this issue without the possibility of breaking things downstream. We need to retrieve BigInteger from the API calls.
The json-bigint package looks promising to solve the JSON.parse problem, but this introduces a number | BigInteger type.
The text was updated successfully, but these errors were encountered:
In researching qdrant/qdrant-web-ui#87, this library is where we lose the point ID precision because of the JSON.parse call not supporting big integers. I'm not aware of a way to solve this issue without the possibility of breaking things downstream. We need to retrieve BigInteger from the API calls.
The
json-bigint
package looks promising to solve the JSON.parse problem, but this introduces a number | BigInteger type.The text was updated successfully, but these errors were encountered: