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.

Sign up for GitHub

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

Jump to bottom

refresh and regenerate graph.json during development based on content structure changes #549

Closed
1 of 5 tasks
thescientist13 opened this issue Apr 11, 2021 · 1 comment
Closed
1 of 5 tasks

refresh and regenerate graph.json during development based on content structure changes #549

thescientist13 opened this issue Apr 11, 2021 · 1 comment
Labels
CLI Content as Data enhancement Improve something existing (e.g. no docs, new APIs, etc)
Milestone
1.0

Comments

@thescientist13
Copy link
Member

thescientist13 commented Apr 11, 2021 •
edited
Loading

Type of Change

  • New Feature Request
  • Documentation / Website
  • Improvement / Suggestion
  • Bug
  • Other (please clarify below)

Summary

When the development server is initially started, it generates a graph.json initially as part of initializing a compilation object. However, if you say change your directory structure or update frontmatter, you will have to restart the GraphQL server to see those updated changes in the client side.

Details

Would be good to find a way to be able to regenerate graph.json, I suppose as part of plugin-standard-html? The thought being that if any HTML / markdown changes, regenerate the whole graph.

A more advanced solution might be able to only update the part that changed, but that would be for bonus and could be a post 1.0 issue.
@thescientist13 thescientist13 added enhancement Improve something existing (e.g. no docs, new APIs, etc) CLI Content as Data labels Apr 11, 2021
@thescientist13 thescientist13 added this to the 1.0 milestone Apr 11, 2021
@thescientist13 thescientist13 mentioned this issue Apr 11, 2021
Closed
53 tasks
@thescientist13
Copy link
Member Author

duplicated by #1278

@thescientist13 thescientist13 closed this as not planned Won't fix, can't repro, duplicate, stale Nov 1, 2024
@github-project-automation github-project-automation bot moved this from 📋 Backlog to ✅ Done in [Greenwood] Phase 11 - Burndown to 1.0 Nov 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
CLI Content as Data enhancement Improve something existing (e.g. no docs, new APIs, etc)
Projects
None yet
Milestone
1.0
Development

No branches or pull requests
1 participant
@thescientist13