-
-
Notifications
You must be signed in to change notification settings - Fork 602
refactor: moved wait and analysis stores to pinia #1918
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
base: develop
Are you sure you want to change the base?
Changes from all commits
ac1f4f8
a8ffde2
300d450
9106c11
0c608c5
86911e1
bcd51c8
fde7480
ea7fb1c
fb31ac6
c48da94
b849d4b
2c3d5c4
72a6c9a
43ec38b
3aeab67
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
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.
low. Relative
'../../stores/wait'here, but@/stores/analysisinsrc/store/index.ts(and'../stores/wait'on the line above it) — three styles for the same target.Given
src/stores/sits one character away from the existingsrc/store/, mixed relative paths between the two trees are a real typo hazard:../stores/…mistyped as../store/…resolves to a different, existing directory and silently imports the wrong thing. Suggest standardising on@/stores/…everywhere, and possibly a less collision-prone directory name (src/pinia/).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.
Yup, that's my error, ill standardize to '@/'
I see valid concern here about store/stores. I took the naming from Pinia's migration guide regarding stores. End state @/stores makes a more descriptive folder structure for maintainability long term and fits the style of the rest of the code base where folders are generally descriptive by function rather than library. How would you like to proceed?
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.
Thank you, please continue with
@/storesplan, and keep an eye to make sure there are no leftovers on@/storeafter migration.