Skip to content

Conversation

@ErnestKz
Copy link
Contributor

@ErnestKz ErnestKz commented Mar 4, 2024

Frontend can begin gradually using this.

I have noticed some unusual behaviour when icepeak.spec.mts is executed (it's testing the simplified icepeak interface). It's that when there's a subscriber listening to /root/sub1, and then when updating /root/sub1, it seems as if only the subscriber listening to /root received an update. This could be because I don't have a reliable way to wait until the subscriber has been subscribed on the server (since it is the simple interface)

Whereas icepeak-core.spec.mts has the correct behaviour, and this could be because I am waiting for the subscription to finish before pushing the updated value to icepeak.

@ErnestKz ErnestKz changed the title Icepeak Icepeak TS Client Mar 4, 2024
@ErnestKz
Copy link
Contributor Author

ErnestKz commented Mar 4, 2024

Todos:

  • Make library consumable
  • More comprehensive docs
  • Add destructor to icepeak
  • Separate react-hook library from the rest
  • Add some re-usable retriers as part of the library
  • Expose first received value from subscription success payload

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant