You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It'd be great to have a feature that would add a projects dependency to an insight page. To start with, parsing a package.json would allow us to "watch" all the dependencies of a project.
Suggested solution
This probably deserves its own RFC, but as a stub, this could exist as something like:
$ pizza parse ./package.json
A few things to consider and edge cases to think about:
Insight pages exist within (and as individual entities for) workspaces. Before moving forward with this implementation, we'd need Feature: workspaces support #74 workspaces support in the CLI
Being able to denote an existing insight page that a project uses would be useful. Maybe we even think about a ~/.pizzacache (or something) that can denote the associate package json files with a given workspace/insight page
Additional context
No response
Code of Conduct
I agree to follow this project's Code of Conduct
Contributing Docs
I agree to follow this project's Contribution Docs
The text was updated successfully, but these errors were encountered:
Type of feature
🍕 Feature
Current behavior
It'd be great to have a feature that would add a projects dependency to an insight page. To start with, parsing a
package.json
would allow us to "watch" all the dependencies of a project.Suggested solution
This probably deserves its own RFC, but as a stub, this could exist as something like:
A few things to consider and edge cases to think about:
~/.pizzacache
(or something) that can denote the associate package json files with a given workspace/insight pageAdditional context
No response
Code of Conduct
Contributing Docs
The text was updated successfully, but these errors were encountered: