-
Notifications
You must be signed in to change notification settings - Fork 14
README for users of this tool #53
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
Draft
paulgries
wants to merge
2
commits into
main
Choose a base branch
from
cave-readme
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,57 @@ | ||
| # Clean Architecture Visualizer (web app) | ||
|
|
||
| This directory contains the web application for the Clean Architecture Visualizer project. It exposes a browser-based UI for exploring Clean Architecture “engines” and their interactions. | ||
|
|
||
| ## Prerequisites | ||
|
|
||
| - Node.js and npm installed. | ||
| - Git installed (if you are cloning the repo). | ||
|
|
||
| ## Installation | ||
|
|
||
| Clone the repository (if you have not already): | ||
|
|
||
| ```bash | ||
| git clone https://github.com/paulgries/Clean-Architecture-Visualizer.git | ||
| cd Clean-Architecture-Visualizer | ||
| ``` | ||
|
|
||
| Install dependencies for the web app: | ||
|
|
||
| ```bash | ||
| cd clean-architecture-visualizer | ||
| npm install | ||
| npm run build | ||
| npm link | ||
| ``` | ||
|
|
||
| ## Running the app | ||
|
|
||
| Start the development server: | ||
|
|
||
| ```bash | ||
| cave view <filepath> | ||
|
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This works with the
|
||
| ``` | ||
|
|
||
| This will start the frontend (and any backend services configured in this package). Check the console output for the local URL (typically http://localhost:5173 or similar, depending on the dev setup). | ||
|
|
||
| ## Running tests | ||
|
|
||
| To run the backend/unit tests: | ||
|
|
||
| ```bash | ||
| npm test | ||
| ``` | ||
|
|
||
| The Jest configuration for the backend lives in jest.config.js, and backend tests are under tests/backend/. | ||
|
|
||
| ## Project structure | ||
|
|
||
| Key subdirectories and files: | ||
| - src/ – Backend/core logic for the visualizer. | ||
| - frontend/ – Frontend code for the UI. | ||
| - tests/backend/ – Backend tests. | ||
| - examples/ – Example projects and data used with the visualizer. | ||
| - package.json – Scripts and dependencies for this package. | ||
|
|
||
| For higher-level context about the overall project, see the top-level README.md in the repository root. | ||
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tried following this and it fails at the
npm linkstep:@matt-dahlgren is this the expected behavior right now?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes it is.
npm linkis used for local development (so that we can test our cli locally without needing to publish/fully download a package) as seen here in the documentation.I will be addressing how to properly download
caveon my next task in documentation. But we are going to deploy it similarly asMemoryVizis deployed.If you see here it is an npm download of the repo itself. This change will include a small addition of a
package.jsonto the outermost layer of this project. But it will allow for faster bug changes.TLDR: npm link is used in development, it is not useable in production as it is looking for a local directory to build.