feat: add workspace component inspect command (#119) - #183
Open
zekelinAlex wants to merge 2 commits into
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
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.
Adds
txc workspace component inspect(exposed over MCP asworkspace_component_inspect), a read-only drill-down into a single component of the local workspace. Forms print the tab > section > control tree with datafieldname bindings, entities print their attributes with types and required levels, views print columns, sort order and the fetch query. Text mode renders a tree/table, JSON mode returns the structured result for agents.The workspace is loaded with
XmlWorkspaceReaderfrom the nearest solution root (walks up toOther/Solution.xml).--idtakes a GUID or a display name (for dialogs also the unique name),--entitynarrows name matches when several entities share a form/view name,--depthtruncates the form tree (1 = tabs, 2 = +sections). Name collisions fail with the list of matching GUIDs instead of picking one silently.Closes #119