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

Docs: Stackblitz missing #15456

Closed
r3ps4J opened this issue May 5, 2024 · 2 comments
Closed

Docs: Stackblitz missing #15456

r3ps4J opened this issue May 5, 2024 · 2 comments
Labels
Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible

Comments

@r3ps4J
Copy link
Contributor

r3ps4J commented May 5, 2024

Describe the bug

There used to be a stackblitz button available when hover a code block on the docs. This was a very helpful feature because the full code doesn't show the actual full code, services and stuff are not shown. Now this is gone, see the screenshot below.

image

There used to be a a lightning bolt icon which would open the stackblitz, similar to this (taken from the primevue docs):

image

Environment

I used https://primeng.org/table when I discovered that it's missing.

Reproducer

N/A

Angular version

N/A

PrimeNG version

N/A

Build / Runtime

Angular CLI App

Language

ALL

Node version (for AoT issues node --version)

N/A

Browser(s)

Firefox

Steps to reproduce the behavior

  1. Open https://primeng.org/
  2. Click "Get Started"
  3. Choose a random component from the sidebar under "Components"
  4. Hover your mouse over a code block
  5. See that the stackblitz icon is not there anymore

Expected behavior

The stackblitz icon should be there

@r3ps4J r3ps4J added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label May 5, 2024
@mertsincan
Copy link
Member

Hi,

So sorry for the delayed response! Improvements have been made to many components recently, both in terms of performance and enhancement. Therefore, this improvement may have been developed in another issue ticket without realizing it. You can check this in the documentation. If there is no improvement on this, can you open a new issue so we can include it in our roadmap?

Thanks a lot for your understanding!
Best Regards,

@r3ps4J
Copy link
Contributor Author

r3ps4J commented Dec 16, 2024

Why do you guys always copy paste this response instead of looking into the issue to confirm it's still a problem?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible
Projects
None yet
Development

No branches or pull requests

2 participants