Conversation
Member
Author
|
@chenIshi, please take a look. We need to add a testing pipeline to ensure our examples remain correct when we make changes. |
Collaborator
|
Indeed this is a better approach, the previous approach is too dirty, with this aligned naming and the environment/ dependency import the code structure is nicer. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Adjusted project structure so we have proper packages we can import into the examples.
Moved telemetry files like langgraph_otel and ADK_otel into a dedicated package - maestro.telemetry_helpers.
Added base maestro CLI with run functionality to be implemented.