-
Notifications
You must be signed in to change notification settings - Fork 68
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
RFC: public/private separation #1244
Conversation
Contents of
|
starfish autocomplete:
|
7bef9c5
to
abb1932
Compare
I see that I dropped it too, but I think Otherwise this LGTM from the end-user perspective. |
Codecov Report
@@ Coverage Diff @@
## master #1244 +/- ##
==========================================
- Coverage 88.86% 86.47% -2.39%
==========================================
Files 140 146 +6
Lines 5244 5524 +280
==========================================
+ Hits 4660 4777 +117
- Misses 584 747 +163
Continue to review full report at Codecov.
|
1f98d98
to
528b575
Compare
I didn't move |
I mean: it should be imported by default. |
Was it done so previously? |
fb6f366
to
aa84692
Compare
Some basic rules of thumb: 1. `starfish.core` code should never reference `starfish`. 2. tests in `starfish.core` should generally reference `starfish` whenever possible. exception: imports in tests for package X should use relative imports to its enclosing package whenever possible. for example, importing `ImageStack` from `ImageStack` tests should be done as `from ..imagestack import ImageStack`. Rationale: it's easy to move code around without breaking references. 3. notebook/vignette code should never use `starfish.core`. I also created some public APIs where they did not previously exist. Basically, go check out what was added in `starfish/`
aa84692
to
99718e8
Compare
I want to let @ambrosejcarr or @shanaxel42 do the actual PR review, but I really dig the API changes here |
By the way, this is passing all notebooks 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.
fiiiiiiine
Some basic rules of thumb:
starfish_impl
code should never referencestarfish
.starfish_impl
should generally referencestarfish
whenever possible. exception: imports in tests for package X should use relative imports to its enclosing package whenever possible. for example, importingImageStack
fromImageStack
tests should be done asfrom ..imagestack import ImageStack
. Rationale: it's easy to move code around without breaking references.starfish_impl
.I also created some public APIs where they did not previously exist. Basically, go check out what was added in
starfish/