Refactor reflection event handling and improve path resolution in Vit… #75
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
Refactor reflection event handling and improve path resolution in Vit…
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.
1-Vite Configuration Update for Robust Path Aliasing:
Modified [vite.config.ts] to use fileURLToPath from the node:url module when resolving the '@' alias. This enhances the reliability of path resolution, particularly for Windows environments, preventing potential issues with module imports that use this alias.
Bug Fix for Reflection Event Handling in App.tsx:
2-Updated the onUpdateEvent handler in [App.tsx].
Specifically, within the logic for processing event.reflection, a defensive check has been added. The code now verifies that event.reflection.follow_up_queries is a valid, non-empty array before attempting to call the .join(',') method on it. This prevents a runtime TypeError that could occur if follow_up_queries was undefined or empty, ensuring smoother handling of reflection events from the LangGraph SDK.