--- tags: [gradio-custom-component, SimpleTextbox, custom-component-track, agents, code-analysis, agents-mcp-hackathon] title: gradio_codeanalysisviewer short_description: A nicer view to show the Agentic code analyser outputs colorFrom: blue colorTo: yellow sdk: gradio pinned: false app_file: space.py --- # `gradio_codeanalysisviewer` PyPI - Version A nicer view to show the Agentic code analyser outputs ## Installation ```bash pip install gradio_codeanalysisviewer ``` ## Usage ```python import gradio as gr from gradio_codeanalysisviewer import CodeAnalysisViewer # Prepare an example dictionary matching the OutputSchema structure example_data = { "code": "def greet(name):\n print(f\"Hello, {name}!\")\n\ngreet(\"User\")", "issue": "Security Risk: Use of f-string in print might be risky if 'name' is user-controlled and not sanitized.", "reason": "Formatted string literals (f-strings) can be vulnerable to injection if they include unsanitized user input, though in this specific 'print' case, the direct risk is low unless the output is piped elsewhere or has special terminal interpretations.", "fixed_code": "def greet(name):\n # Sanitize name if it comes from an external source, e.g., name = escape(name)\n print(f\"Hello, {name}!\")\n\ngreet(\"User\")", "feedback": "#### Security Feedback:\n* **Issue**: Potential for injection with f-string.\n* **Severity**: Low (in this context).\n* **Recommendation**: Always sanitize external inputs used in f-strings, especially if they are logged or displayed in sensitive contexts. For simple printing, the risk is minimal.\n\n#### Documentation Feedback:\n* The function `greet` is missing a docstring.\n* Consider adding type hints." } # Use the example_value from the component itself for the examples list # This ensures we're using the structure defined within the component's backend component_example = CodeAnalysisViewer().example_value() demo = gr.Interface( lambda data_dict: data_dict, # The function now expects and returns a dictionary CodeAnalysisViewer(label="Input Analysis (Interactive - if it were input)"), # This would be for input, not our primary use case CodeAnalysisViewer(label="Code Analysis Output"), # This is how we'll use it as an output display examples=[[component_example], [example_data]] # Provide examples ) if __name__ == "__main__": demo.launch() ``` ## `CodeAnalysisViewer` ### Initialization
name type default description
value ```python dict | Callable | None ``` None default text to provide in textbox. If a function is provided, the function will be called each time the app loads to set the initial value of this component.
placeholder ```python str | None ``` None placeholder hint to provide behind textbox.
label ```python str | I18nData | None ``` None the label for this component, displayed above the component if `show_label` is `True` and is also used as the header if there are a table of examples for this component. If None and used in a `gr.Interface`, the label will be the name of the parameter this component corresponds to.
every ```python Timer | float | None ``` None Continously calls `value` to recalculate it if `value` is a function (has no effect otherwise). Can provide a Timer whose tick resets `value`, or a float that provides the regular interval for the reset Timer.
inputs ```python Component | Sequence[Component] | set[Component] | None ``` None Components that are used as inputs to calculate `value` if `value` is a function (has no effect otherwise). `value` is recalculated any time the inputs change.
show_label ```python bool | None ``` None if True, will display label.
scale ```python int | None ``` None relative size compared to adjacent Components. For example if Components A and B are in a Row, and A has scale=2, and B has scale=1, A will be twice as wide as B. Should be an integer. scale applies in Rows, and to top-level Components in Blocks where fill_height=True.
min_width ```python int ``` 160 minimum pixel width, will wrap if not sufficient screen space to satisfy this value. If a certain scale value results in this Component being narrower than min_width, the min_width parameter will be respected first.
interactive ```python bool | None ``` None if True, will be rendered as an editable textbox; if False, editing will be disabled. If not provided, this is inferred based on whether the component is used as an input or output.
visible ```python bool ``` True If False, component will be hidden.
rtl ```python bool ``` False If True and `type` is "text", sets the direction of the text to right-to-left (cursor appears on the left of the text). Default is False, which renders cursor on the right.
elem_id ```python str | None ``` None An optional string that is assigned as the id of this component in the HTML DOM. Can be used for targeting CSS styles.
elem_classes ```python list[str] | str | None ``` None An optional list of strings that are assigned as the classes of this component in the HTML DOM. Can be used for targeting CSS styles.
render ```python bool ``` True If False, component will not render be rendered in the Blocks context. Should be used if the intention is to assign event listeners now but render the component later.
key ```python int | str | tuple[int | str, ...] | None ``` None in a gr.render, Components with the same key across re-renders are treated as the same component, not a new component. Properties set in 'preserved_by_key' are not reset across a re-render.
preserved_by_key ```python list[str] | str | None ``` "value" A list of parameters from this component's constructor. Inside a gr.render() function, if a component is re-rendered with the same key, these (and only these) parameters will be preserved in the UI (if they have been changed by the user or an event listener) instead of re-rendered based on the values provided during constructor.
### Events | name | description | |:-----|:------------| | `change` | Triggered when the value of the CodeAnalysisViewer changes either because of user input (e.g. a user types in a textbox) OR because of a function update (e.g. an image receives a value from the output of an event trigger). See `.input()` for a listener that is only triggered by user input. | | `input` | This listener is triggered when the user changes the value of the CodeAnalysisViewer. | | `submit` | This listener is triggered when the user presses the Enter key while the CodeAnalysisViewer is focused. | ### User function The impact on the users predict function varies depending on whether the component is used as an input or output for an event (or both). - When used as an Input, the component only impacts the input signature of the user function. - When used as an output, the component only impacts the return signature of the user function. The code snippet below is accurate in cases where the component is used as both an input and an output. - **As output:** Is passed, the payload to be used in the backend function. - **As input:** Should return, expects a dictionary (OutputSchema) from the backend function. ```python def predict( value: dict | None ) -> dict | None: return value ```