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
This has been discussed on our roundtable on March 31st. We will start implementing it gradually to different endpoints. The idea is to type the expected shape array with the return type of a given function.
Here is a dump of the proposal:
rationale:
it has happened to us several times already that the responses from bee version we officially supported did not match the bee-js type
as far as I recall, in 2 cases it was missing properties, in one case it was wrong type of properties and in one it was removed property
I think this was already once or twice brought up before but we have never really decided to do this.
From my POW I am done doing it, especially as we are promising some returned types/interfaces from the API calls that we are not really sure if it is correct or not.
This has been discussed on our roundtable on March 31st. We will start implementing it gradually to different endpoints. The idea is to type the expected shape array with the return type of a given function.
Here is a dump of the proposal:
rationale:
proposal:
The text was updated successfully, but these errors were encountered: