urbit / bridge

An application for interacting with Azimuth.
MIT License
98 stars 25 forks source link

details-store: try both L1 and L2 when syncing details #941

Closed arthyn closed 2 years ago

arthyn commented 2 years ago

So I'm not entirely sure this is right, but from what I could glean, it seems like the roller API was failing to find the new L1 point throwing an error from api.getPoint, so the L1 point details never get synced? This just adds a backup call to try getting the point from azimuth similar to what you see in the useRoller hook under initPoint. This seems to fix #892