Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Data doesn't show up for published.wallet.xxx #2

Closed
samsiegart opened this issue Oct 4, 2024 · 0 comments · Fixed by #3
Closed

Data doesn't show up for published.wallet.xxx #2

samsiegart opened this issue Oct 4, 2024 · 0 comments · Fixed by #3
Assignees

Comments

@samsiegart
Copy link

Repro steps:

Expected behavior:

  • Data appears in the below section

Context:

Perhaps this has something to do with the fact that the node has data as well as children. When you go to a leaf node, like published.wallet.xxx.current, the data renders perfectly fine.

Screenshot

Screen Shot 2024-10-04 at 11 16 17 AM
@turadg turadg self-assigned this Dec 10, 2024
This was referenced Dec 11, 2024
@turadg turadg closed this as completed in #3 Dec 11, 2024
mergify bot added a commit to Agoric/agoric-sdk that referenced this issue Dec 11, 2024
_incidental_

refs: agoric-labs/vstorage-viewer#2

## Description
In the course of working on agoric-labs/vstorage-viewer#3 it was hard to work with an async `makeVstorageKit`. It was async because construction of the kit required fetching a bunch of data from vstorage to populate `agoricNames`.

That concern is a higher level than vstorage so this pulls it out. That allows `makeVstorageKit` to be synchronous.

I added a test of `makeAgoricNames` both before and after.

Eventually I think something should make it easy to make an AgoricNamesKit that wraps `VstorageKit` the way `VstorageKit` wraps `Vstorage`. `makeWalletUtils` does that but needs more work. At least renaming to `SmartWallet` but it would help to have a rethink of the layering and vstorage decoding in client-utils.

### Security Considerations
none

### Scaling Considerations
none

### Documentation Considerations
not documented but this will make it less complex

### Testing Considerations
new test

While refactoring, tsc really let me down by not detecting destuctured properies that were no longer on the source object. I suppose our settings aren't strict enough. I enabled `noImplicitAny` to detect those (by then filtering for makeVstorageKit)

### Upgrade Considerations
n/a
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 a pull request may close this issue.

2 participants