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
Currently, both our get and view notes functions support passing an offset which can be used for pagination. However, it need to be supported by the application to actually be used.
I'm not sure we can really push this to devs as it is quite easy to forget it, so possibly it is better to see if we should feed in the value from an oracle, which have a base-value of 0. For example, say that we use a get_note_offset_oracle which is used when viewing or getting notes. Offset can then be used without needing to alter applications, and should allow us to execute a .view() along with updates offset such that we can handle fetching "all" notes in ts side of things by looking through notes and extending the offset until no more notes are found.
The text was updated successfully, but these errors were encountered:
See comment from @rahul-kothari in #2806.
Currently, both our get and view notes functions support passing an
offset
which can be used for pagination. However, it need to be supported by the application to actually be used.I'm not sure we can really push this to devs as it is quite easy to forget it, so possibly it is better to see if we should feed in the value from an oracle, which have a base-value of 0. For example, say that we use a
get_note_offset_oracle
which is used when viewing or getting notes. Offset can then be used without needing to alter applications, and should allow us to execute a.view()
along with updates offset such that we can handle fetching "all" notes in ts side of things by looking through notes and extending the offset until no more notes are found.The text was updated successfully, but these errors were encountered: