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

Result field #366

Open
JohnCoene opened this issue Apr 29, 2024 · 2 comments
Open

Result field #366

JohnCoene opened this issue Apr 29, 2024 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@JohnCoene
Copy link
Member

@nbenn In addition to the issues previously mentioned about not being able to restore "linked" stacks I think this is at the core of it.

The value of a result_field is not the reference to the other stack but the data of the said stack where I think the value of the result_field should be the stack name as selected in the generated select_input.

The above breaks a few things like ui_input which attempts to set the selected value in the dropdown to a dafa.frame: from a result field it is impossible to trace back which stack the data came from, both of these make it impossible to restore a stack I think.

@nbenn
Copy link
Collaborator

nbenn commented Jun 11, 2024

Provide a value() implementation for the result_field to fetch the data instead of storing it with the field.

@JohnCoene JohnCoene added the bug Something isn't working label Aug 23, 2024
@JohnCoene
Copy link
Member Author

@nbenn do you have any news on this? I'm asking because we really need for the POC demo in 2 weeks and also to stress test blockr.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants