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

Documentation for CdsGrid not working properly #304

Open
3 of 8 tasks
squidjam opened this issue Apr 19, 2024 · 3 comments
Open
3 of 8 tasks

Documentation for CdsGrid not working properly #304

squidjam opened this issue Apr 19, 2024 · 3 comments

Comments

@squidjam
Copy link

squidjam commented Apr 19, 2024

Describe the bug

Documentation for the CdsGrid component is not working properly. The following is a screenshot (easier than try to describe it)
image

How to reproduce

Go here and take a look

Expected behavior

The component documentation should be presented correctly, even if it's still up for discussion how the component should be.

Versions

Clarity project:

  • Clarity Core
  • Clarity Angular/UI

Clarity version:

  • v5.x
  • v6.x

Framework:

  • Angular
  • React
  • Vue
  • Other: I don't know which framework do you use in the one you have in the docs.

Framework version:
N/A

Device:

  • Type: Dell Laptop
  • OS: Windows 11
  • Browser Chrome
  • Version latest

Additional notes

In console one gets these messages:

Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'cells')
    at 7d8f7d84.js:7734:48
    at Array.map (<anonymous>)
    at n.render (7d8f7d84.js:7730:24)
    at n.update (7d8f7d84.js:34:561)
    at n.performUpdate (7d8f7d84.js:28:4861)
    at n.scheduleUpdate (7d8f7d84.js:28:4508)
    at n._$E_ (7d8f7d84.js:28:4416)
Uncaught TypeError: Cannot read properties of undefined (reading 'find')
    at 7d8f7d84.js:7562:153
(anonymous) @ 7d8f7d84.js:7562
@kevinbuhmann
Copy link
Member

The CdsGrid is not a completed nor supported component.

@squidjam
Copy link
Author

The CdsGrid is not a completed nor supported component.

Does this mean it's not a good idea to report when the documentation breaks?

@squidjam
Copy link
Author

Plink

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