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

[Bug]: Value of select component get not updated #692

Open
1 task done
der-berni opened this issue Feb 20, 2024 · 5 comments
Open
1 task done

[Bug]: Value of select component get not updated #692

der-berni opened this issue Feb 20, 2024 · 5 comments
Labels
Bug Something isn't working Needs triage Needs to be reviewed by core team

Comments

@der-berni
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

I have created a select component from a sql query or mapped the data from an array.
The value is not changed. Not even in the preview.
Animation

Expected Behavior

The value schuld be changed. In the Playground it work like expected.
https://app.lowcoder.cloud/playground/select/1

Animation

Steps to reproduce

Create a select component with "Map" and Data: [{id:0,name:test0},{id:1,name:test1}]

Environment

lowcoder running in docker with: lowcoderorg/lowcoder-ce-frontend:latest
Version: 2.3.0-#92196587

Additional Information

No response

@der-berni der-berni added Bug Something isn't working Needs triage Needs to be reviewed by core team labels Feb 20, 2024
@yofriadi
Copy link

not sure, but there is change lately in this component regarding how it update it's value here

@superlaser97
Copy link

superlaser97 commented Feb 21, 2024

+1

I am having the same issue, the select.value is not updated. All my apps using this component broke

image

@dizzy-duality
Copy link

dizzy-duality commented Feb 21, 2024

Can confirm the same on the latest dockers (front/node/api) service on google cloud-run. Moved back to 2.3 all seems good from there.

@FalkWolsky
Copy link
Contributor

We fixed it now. It will be contained in the 2.3.1 release

@FalkWolsky
Copy link
Contributor

Sometimes one wants to make it right - but we forgot the "past".
Background is, that we separated the "Default Value" from the "actual value" in the select.
This was important, since we had the state, that when you set a Default Value, it would not change by user action and so the user action was not taken into account in connected Components like "List".

We introduced the Default Value "next" to the "value" - but that means, that as for "today" you would need to touch all apps and set a Default value. This is possible - but not the good approach from us. So we work in the next days a solution, where this small "touch" will happen automatically, so existing apps will work then "again".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working Needs triage Needs to be reviewed by core team
Projects
None yet
Development

No branches or pull requests

5 participants