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

type images generation should be smarter #1206

Closed
coke opened this issue Feb 20, 2017 · 3 comments
Closed

type images generation should be smarter #1206

coke opened this issue Feb 20, 2017 · 3 comments
Labels
wishlist "nice to have" issues; might require a lot of work or a big change or be low priority

Comments

@coke
Copy link
Collaborator

coke commented Feb 20, 2017

Currently the type graph images are generated or not based on the presence of a single file.

Ideally we should only be generating the files we need (and that includes only a subset of these files if we do a --sparse run)

This is a low priority item.

@coke coke added the build label Feb 20, 2017
@JJ
Copy link
Contributor

JJ commented Apr 7, 2018

I wonder if this is needed. After all, it's much faster now after the latest changes to htmlify.p6

@coke coke self-assigned this Apr 9, 2018
@JJ JJ added the wishlist "nice to have" issues; might require a lot of work or a big change or be low priority label Jul 28, 2018
@coke coke removed their assignment Sep 27, 2019
@2colours
Copy link
Contributor

First, this issue would probably belong to the doc-website repo now - and is it even relevant these days?

@coke
Copy link
Collaborator Author

coke commented Mar 1, 2023

Correct, this ticket no longer relevant on this repo.

@coke coke closed this as not planned Won't fix, can't repro, duplicate, stale Mar 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wishlist "nice to have" issues; might require a lot of work or a big change or be low priority
Projects
None yet
Development

No branches or pull requests

3 participants