[WIP] Slim version of TaskDoc for production #1232
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
clean up class def to reflect current utililty
+ utility decorators for customizing arrow type introspection behavior
… to help with arrow roundtriping
…th arrow + add optimade to optional deps for testing - needed due to walking emmet to import all pydantic models
|
Will do! Yeah the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Will be considered experimental until performance + compatibility with builder/api client can be tested
@esoteric-ephemera, check if the field split I made here makes sense. Can worry about model validators and a parsing method later after I've tested the basic schema works for the build pipelines + api
Based this branch off your
alpha_idbranch for the updatedtask_idtyping.Also makes more sense for the top level
outputfield to be the calc output right?