Skip to content

[CHORE] Updating Vis and fixing TypeScript errors. #1447

@JU12000

Description

@JU12000

Hi, I'm currently using Compodoc with Storybook to generate documentation for a UI component library. However, my organization has very strict security policies which are flagging Compodoc for it's reliance on vis which is marked end of life. To that end I decided I would open an issue and perhaps create a draft PR if you're receptive to update to vis-chart which replaces vis.

I started working on the draft PR but realized I can't build Compodoc because of the number of TypeScript errors. I was going to open a PR to fix as many of these as I could but I wanted to check first that doing so wouldn't hinder any work you're doing already or result in double work if you're migrating code.

I'd really like to continue using Compodoc and would be willing to contribute to fix these issues, but I'm unsure of the path forward which causes the least disruption for you.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions