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

problems with boolean types: vue warnings, and interface and displays can not be changed #7429

Closed
3 tasks done
ludi81 opened this issue Aug 16, 2021 · 0 comments · Fixed by #7460
Closed
3 tasks done
Assignees
Labels

Comments

@ludi81
Copy link

ludi81 commented Aug 16, 2021

Preflight Checklist

Describe the Bug

Hi,

I just used the source version of rc.90.
I created a new collection with two boolean columns within directus.
At the first boolean variable I choose boolean and pressed afterwards always next (without selecting the interface and display).
At the second boolean variable I choose boolean and selected the standard at the interface and display step.

After adding a new row to the collection (with admin) I see multiple warnings in the browser:
e.g.

Invalid prop: type check failed for prop "value". Expected Boolean, got Number with value 0. at <Boolean key=1 autofocus=false disabled=false ... >

If I try to edit the one column I am not able to change the interface and display options. The first one shows an integer.

2021-08-16_14-27-27

At previous versions I was able to change the interface type afterwards.
Thanks

To Reproduce

see above

What version of Directus are you using?

rc90

What version of Node.js are you using?

v16.1.0

What database are you using?

mysql

What browser are you using?

chrome

What operating system are you using?

macOS

How are you deploying Directus?

running locally with the source from github

@Nitwel Nitwel self-assigned this Aug 17, 2021
@Nitwel Nitwel added the API label Aug 17, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 3, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants