Source command#33
Merged
Merged
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
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.
This PR introduced as new CLI command that I thought would be useful when working with agents. Commonly, an agent will successfully query data about entities, but if those are then to be edited, a workspace-wide grep needs to be performed to find the source file to edit.
firm sourcehelps this process along by explicitly getting the source file path for a given entity or schema. This helps reduce ambiguity when combining CLI and raw-DSL workflows.We achieve this in a simple way by searching parsed DSL from the workspace. This can be achieved before workspace + graph is built. So long as workspaces aren't huge, I'm thinking this is performant enough for a one-off without mixing concerns by storing source paths in internal data models.
Reference:
Arguments:
target_type- Entity type (e.g.,person,organization) orschematarget_id- Entity ID or schema nameExamples: