209 sample project structure #242
Merged
Conversation
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
Yordan-Ramchev
approved these changes
Mar 27, 2024
|
@georgi-mateev @stanislavmihaylov |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Pull Request
Description
Goal is the user to have an option to create a sample project using pinia, vue-router, vitest and provide an example file structure.
Related Issue
#209
Checklist
Notes for Reviewers
We chose to have this rigid of a structure in order to circumvent the need for rendering the base config - if we don't we will need to handle the sample project case in all the utils that create, traverse or modify files, make sure it is not getting overwritten and it generally feels like making the flow too complex.
From here on we can break out in tasks and modify the Vue app- customize it to our brand, create components, stores and shape it to our vision.