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]: DataGridProps is any #33485

Closed
2 tasks done
cemcakirlar opened this issue Dec 18, 2024 · 3 comments
Closed
2 tasks done

[Bug]: DataGridProps is any #33485

cemcakirlar opened this issue Dec 18, 2024 · 3 comments

Comments

@cemcakirlar
Copy link

Component

DataGrid

Package version

9.56.6

React version

19.0.0

Environment

System:
    OS: macOS 15.1.1
    CPU: (12) arm64 Apple M4 Pro
    Memory: 1.22 GB / 24.00 GB
    Shell: 5.9 - /bin/zsh
  Browsers:
    Edge: 131.0.2903.99
    Safari: 18.1.1

Current Behavior

DataGrid component is typed as any. Cannot get autocomplete in VSCode for properties.

Expected Behavior

It should be typed correctly.

Reproduction

The issue seems trivial.

Steps to reproduce

Use DataGrid and try to add props in a typescript project. Mine is a NextJS project

Are you reporting an Accessibility issue?

None

Suggested severity

High - No workaround

Products/sites affected

No response

Are you willing to submit a PR to fix?

no

Validations

  • Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
  • The provided reproduction is a minimal reproducible example of the bug.
@cemcakirlar
Copy link
Author

cemcakirlar commented Dec 18, 2024

How it looks in VSCode :)

Image Image

@layershifter
Copy link
Member

Duplicate, see #33482 (comment).

@cemcakirlar
Copy link
Author

thank you for showing me the right issue, one comment I want to add is, people may start searching type checks, typing issue, props are not visible etc. I accept that I did not made a rigorous search for the issue but I just saw that other components are also affected the same way. hence the datagrid mention. I suggest that the real issue should contain some right keywords to pin point. again thanks for the help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants