-
Notifications
You must be signed in to change notification settings - Fork 6
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
Feature/traitlets refactor #55
Conversation
…traitlets more explicitly to indicate attributes and parameters.
…_select module. Also moving the 'tests' to a unit test. This needs to be cleaned up.
…the new 'method' into a number of execute methods.
…e. This is a big one...
# Conflicts: # podpac/core/data/data.py
I'd like this one merged in sooner than later so we can start working using the same methodology. |
Pull Request Test Coverage Report for Build 133
💛 - Coveralls |
@mpu-creare This was the first thing I tried to do.
Here's the result:
Are the tagged attrs supposed to be loaded in the the |
@mpu Well, no, actually I'm guessing that either
|
Yep, that was another mistake on my part. |
* CoordData should have used coord_name as an attr, not a parameter * CoordData should raise exception if coord_name not in evaluated_coordinates * ReprojectedSource should still inherit from Algorithm to allow coordinates_source to be specified as an input
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.
Looks great, seems pretty clear. I guess we need these two tags to be documented somewhere, probably we need a "Writing Custom Nodes" user guide and we would describe these there.
Agreed. Feel free to start a doc stub, or assign that task to me. |
This modifies the way we use Traitlets. It inegrates more tightly with traitlets, requiring traits to be tagged. This tagging can the be used to more accurately and robustly create pipelines.
Also adding a large amount of documentation in the PR.