Add Gradio web interface for standards registry #1

eswarchandravidyasagar · 2025-11-14T01:18:13Z

Add standards_registry.py with full Gradio UI
Add interactive data tables with horizontal scrolling
Add search functionality across standards
Add .gitignore for Python project
Update README with web interface documentation
Update pyproject.toml configuration

- Add standards_registry.py with full Gradio UI - Add interactive data tables with horizontal scrolling - Add search functionality across standards - Add .gitignore for Python project - Update README with web interface documentation - Update pyproject.toml configuration

Copilot

Pull Request Overview

This PR adds a Gradio-based web interface for browsing and interacting with the standards registry, along with supporting configuration files and documentation updates.

Introduces a complete web UI with browse, search, and data viewing capabilities
Adds Python project configuration with dependency management
Updates documentation to include web interface usage instructions

Reviewed Changes

Copilot reviewed 3 out of 5 changed files in this pull request and generated 19 comments.

File	Description
standards_registry.py	New Gradio web application providing interactive UI for browsing, searching, and viewing standards with data tables and statistics
pyproject.toml	Project configuration file defining dependencies (Gradio, PyYAML, watchdog) and build settings
README.md	Documentation updated with web interface installation, usage instructions, and architecture overview
.gitignore	Standard Python gitignore patterns added for virtual environments, build artifacts, IDE files, and Gradio-specific directories

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2025-11-14T01:24:01Z

standards_registry.py

+    for std in standards:
+        stats = registry.get_statistics(std.id)
+        total_records += stats.get("total_records", 0)


The registry overview loads and processes statistics for all standards sequentially within the loop. This can be inefficient if the registry contains many standards with large datasets. Consider caching statistics or loading them in parallel to improve performance:

stats = registry.get_statistics(std.id) if stats: # Only proceed if stats exist total_records += stats.get("total_records", 0)

Copilot · 2025-11-14T01:24:01Z

standards_registry.py

+        return []
+
+    data = registry.load_standard_data(standard_id)
+    if not data:
+        return []
+
+    records = registry._get_data_records(data)
+    if not records or not records[0]:
+        return []
+
+    fields = list(records[0].keys())
+    if not fields:
+        return []


The function get_all_records_table returns an empty list [] for both error cases and when there are truly no records. This makes it impossible for callers to distinguish between different failure modes. Consider returning None for errors or raising exceptions:

def get_all_records_table(standard_id: str, registry: StandardsRegistry): if not standard_id: return None # Or raise ValueError("standard_id is required") # ... rest of the function

Suggested change

return []

data = registry.load_standard_data(standard_id)

if not data:

return []

records = registry._get_data_records(data)

if not records or not records[0]:

return []

fields = list(records[0].keys())

if not fields:

return []

return None

data = registry.load_standard_data(standard_id)

if not data:

return None

records = registry._get_data_records(data)

if not records or not records[0]:

return None

fields = list(records[0].keys())

if not fields:

return None

Copilot · 2025-11-14T01:24:01Z

standards_registry.py

+        path_parts = standard.path.split("/")
+        filename = path_parts[-1]
+        dir_path = "/".join(path_parts[:-1])
+


The path parsing logic using string split/join operations is fragile and platform-dependent. Since standard.path is already being handled as a Path object on line 62, use Path operations consistently:

data_path = self.registry_path / standard.path dir_path = data_path.parent filename = data_path.name

Suggested change

path_parts = standard.path.split("/")

filename = path_parts[-1]

dir_path = "/".join(path_parts[:-1])

filename = data_path.name

dir_path = data_path.parent.relative_to(self.registry_path)

Copilot · 2025-11-14T01:24:02Z

README.md

+Or using `pip`:
+
+```bash
+pip install -r requirements.txt
+```
+


The README references requirements.txt in the installation instructions, but this file doesn't exist in the repository. Since the project uses pyproject.toml for dependency management, either create a requirements.txt file or update the documentation to only mention uv and the pyproject.toml approach.

Suggested change

Or using `pip`:

```bash

pip install -r requirements.txt

```

Copilot · 2025-11-14T01:24:02Z

standards_registry.py

+                    outputs=[data_table, table_status, table_info]
+                )
+                table_standard_dropdown.change(
+                    fn=lambda sid: ("<div class='table-container'><p>Select a standard and click 'Load Table' to view data.</p></div>", f"### Data Table\n\nSelected: {registry.get_standard(sid).title if sid else 'None'}. Click 'Load Table' to view data.", ""),


Potential AttributeError when sid is provided but registry.get_standard(sid) returns None. The lambda attempts to access .title on a potentially None value. Add a safety check:

fn=lambda sid: ("<div class='table-container'><p>Select a standard and click 'Load Table' to view data.</p></div>", f"### Data Table\n\nSelected: {registry.get_standard(sid).title if sid and registry.get_standard(sid) else 'None'}. Click 'Load Table' to view data.", ""),

Suggested change

fn=lambda sid: ("<div class='table-container'><p>Select a standard and click 'Load Table' to view data.</p></div>", f"### Data Table\n\nSelected: {registry.get_standard(sid).title if sid else 'None'}. Click 'Load Table' to view data.", ""),

fn=lambda sid: (

"<div class='table-container'><p>Select a standard and click 'Load Table' to view data.</p></div>",

f"### Data Table\n\nSelected: {(registry.get_standard(sid).title if sid and registry.get_standard(sid) is not None else 'None')}. Click 'Load Table' to view data.",

""

),

Copilot · 2025-11-14T01:24:04Z

standards_registry.py

+        if std.tags:
+            tags_str = ", ".join(f"`{tag}`" for tag in std.tags)
+            overview += f"**Tags:** {tags_str}\n"
+        overview += f"**Description:** {std.description[:150]}...\n\n"


The ellipsis ... is always added regardless of the description length. This results in unnecessary ellipsis for descriptions shorter than 150 characters. Consider adding it conditionally:

desc = std.description[:150] overview += f"**Description:** {desc}{'...' if len(std.description) > 150 else ''}\n\n"

Suggested change

overview += f"**Description:** {std.description[:150]}...\n\n"

desc = std.description[:150]

overview += f"**Description:** {desc}{'...' if len(std.description) > 150 else ''}\n\n"

Copilot · 2025-11-14T01:24:05Z

standards_registry.py

+    signal.signal(signal.SIGINT, signal_handler)
+
+    try:
+        app.launch(share=False, server_name="0.0.0.0", server_port=7860)


The server is configured to bind to all network interfaces (0.0.0.0), making it accessible from any network. This could expose the application to unauthorized access if deployed on a shared network or server. Consider:

Using 127.0.0.1 for local-only access by default

Adding authentication via Gradio's auth parameter

Documenting security considerations in the README

Example:

app.launch(share=False, server_name="127.0.0.1", server_port=7860)

Suggested change

app.launch(share=False, server_name="0.0.0.0", server_port=7860)

app.launch(share=False, server_name="127.0.0.1", server_port=7860)

Copilot · 2025-11-14T01:24:05Z

standards_registry.py

+            return []
+
+        query_lower = query.lower()
+        return [r for r in records if query_lower in " ".join(str(v) for v in r.values() if v).lower()]


The search implementation converts all record values to strings and concatenates them for each record on every search, which is inefficient for large datasets. Consider one of these optimizations:

Pre-build a search index when data is loaded

Use more efficient string matching algorithms

Add pagination to limit the number of records processed

Example:

query_lower = query.lower() results = [] for r in records: record_text = " ".join(str(v) for v in r.values() if v).lower() if query_lower in record_text: results.append(r) if len(results) >= 1000: # Limit results for performance break return results

Copilot · 2025-11-14T01:24:05Z

standards_registry.py

+            elif isinstance(value, str):
+                row.append(value.strip() or "—")
+            elif isinstance(value, (int, float)):
+                row.append(f"{value:,}" if isinstance(value, int) else f"{value:.2f}")


The number formatting for integers uses a comma separator but doesn't account for locale. While this works for English locales, it may not be appropriate for all regions. Consider using the locale module or document this behavior. Additionally, the float formatting always shows 2 decimal places, which may not be appropriate for all numeric data.

Copilot · 2025-11-14T01:24:05Z

standards_registry.py

+        vertical-align: top !important;
+    }
+    .data-table th {
+        background-color: #374151 !important;


The table header background color #374151 (dark gray) with white text may not provide sufficient contrast for users with visual impairments. Consider using a darker background or ensuring the contrast ratio meets WCAG AA standards (minimum 4.5:1 for normal text). You can verify contrast at https://webaim.org/resources/contrastchecker/

Suggested change

background-color: #374151 !important;

background-color: #1f2937 !important;

Copilot AI review requested due to automatic review settings November 14, 2025 01:18

Copilot started reviewing on behalf of eswarchandravidyasagar November 14, 2025 01:18 View session

Copilot finished reviewing on behalf of eswarchandravidyasagar November 14, 2025 01:21

Copilot AI reviewed Nov 14, 2025

View reviewed changes

eswarchandravidyasagar marked this pull request as draft November 14, 2025 14:40

dependency issues fixed

c819bb1

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Add Gradio web interface for standards registry #1

Add Gradio web interface for standards registry #1

Uh oh!

eswarchandravidyasagar commented Nov 14, 2025

Uh oh!

Copilot AI left a comment

Uh oh!

Copilot AI Nov 14, 2025

Uh oh!

Copilot AI Nov 14, 2025

Uh oh!

Copilot AI Nov 14, 2025

Uh oh!

Copilot AI Nov 14, 2025

Uh oh!

Copilot AI Nov 14, 2025

Uh oh!

Copilot AI Nov 14, 2025

Uh oh!

Copilot AI Nov 14, 2025

Uh oh!

Copilot AI Nov 14, 2025

Uh oh!

Copilot AI Nov 14, 2025

Uh oh!

Copilot AI Nov 14, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

	overview += f"Description: {std.description[:150]}...\n\n"
	desc = std.description[:150]
	overview += f"Description: {desc}{'...' if len(std.description) > 150 else ''}\n\n"

	app.launch(share=False, server_name="0.0.0.0", server_port=7860)
	app.launch(share=False, server_name="127.0.0.1", server_port=7860)

	background-color: #374151 !important;
	background-color: #1f2937 !important;

Add Gradio web interface for standards registry #1

Are you sure you want to change the base?

Add Gradio web interface for standards registry #1

Uh oh!

Conversation

eswarchandravidyasagar commented Nov 14, 2025

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull Request Overview

Reviewed Changes

Uh oh!

Copilot AI Nov 14, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Nov 14, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Nov 14, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Nov 14, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Nov 14, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Nov 14, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Nov 14, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Nov 14, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Nov 14, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Nov 14, 2025

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants