-
Notifications
You must be signed in to change notification settings - Fork 323
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
Move utility files to common
package
#11863
base: develop
Are you sure you want to change the base?
Conversation
🧪 Storybook is successfully deployed!📊 Dashboard:
|
Why is this being moved? We don't need a |
|
||
import { | ||
chain, | ||
count as countFn, | ||
empty, | ||
filter, | ||
filterDefined, | ||
last as lastFn, | ||
range, | ||
tryGetSoleValue, | ||
zip, | ||
zipLongest, | ||
} from '../iter' |
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 this change? We usually use the iter
module by qualified import, because it defines a lot of names that are likely to collide with locals.
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.
oh... yeah, my bad. i guess ideally we could record exceptions (?) like these somewhere? just so there's somewhere to refer to when doing refactors
💀 oh yeah i forgor. yeah i just wanted to move the stuff out of the dashboard specific tree |
moved from pinging @Frizi for re-review (although no rush on finishing the review) |
my bad, overly eager moving into |
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.
This PR needs to wait for bazel branch to be merged first. Otherwise we will have an immense amount of conflicts, and it is a priority to finish it first.
Pull Request Description
common
packageImportant Notes
Testing Instructions
N/A. No logic changes present, only moving files.
Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:
The documentation has been updated, if necessary.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.