-
Notifications
You must be signed in to change notification settings - Fork 324
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
Expand parent directories of opened projects #11947
base: develop
Are you sure you want to change the base?
Conversation
🧪 Storybook is successfully deployed!📊 Dashboard:
|
app/gui/src/dashboard/components/dashboard/DirectoryNameColumn.tsx
Outdated
Show resolved
Hide resolved
app/gui/src/dashboard/components/dashboard/column/PathColumn.tsx
Outdated
Show resolved
Hide resolved
app/gui/src/dashboard/layouts/Drive/Categories/categoriesHooks.tsx
Outdated
Show resolved
Hide resolved
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'm not satisfied with the implementation
🚫 Also, We need integration tests for this feature |
@@ -1,83 +0,0 @@ | |||
import { DirectoryId } from '#/services/Backend' |
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.
Why did we remove the tests?
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.
behavior has been changed so these tests are no longer relevant
we can write a new test in the same style if that works?
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 for sure. Unrelevant tests can be removed, but we need to add new ones if we add a new
behavior. Coverage shouldn't decrease
…f in a `useEffect`
@MrFlashAccount wdym by this btw? |
Pull Request Description
Important Notes
None
Testing Instructions
enso/
to local favorites and open project)Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:
The documentation has been updated, if necessary.Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.Scala,
Java,
TypeScript,
and
Rust
style guides. In case you are using a language not listed above, follow the Rust style guide.
Unit tests have been written where possible.If meaningful changes were made to logic or tests affecting Enso Cloud integration in the libraries,or the Snowflake database integration, a run of the Extra Tests has been scheduled.
If applicable, it is suggested to paste a link to a successful run of the Extra Tests.