Feat: Update env vars and add examples to manifest #37
Conversation
There was a problem hiding this comment.
Pull request overview
This PR refactors the environment variable management system and significantly expands the manifest with new examples and metadata. The changes improve maintainability by centralizing environment variable configuration and enhance the registry with additional integrations and documentation links.
Key changes include:
- Refactored environment variable handling with a centralized mapping structure in
registry.ts - Added support for new API keys (Brave, Query) in the constants file
- Expanded manifest with 8 new examples and enhanced existing entries with documentation links and thumbnails
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
| source/utils/registry.ts | Refactored environment variable handling to use a centralized CATEGORY_ENV_MAP structure, moved EnvVar type definition, simplified getEnvironmentVariables function logic, and removed unused stack parameter from mapLanguage |
| source/utils/constants.ts | Added new environment variable mappings for brave_key and query, removed unused TemplateOptions import |
| manifest.json | Updated version to 48170c9, added 8 new examples (Agent Kit, Agno, Browser-use captcha solver, CrewAI, Extensions, Notte, Perplexity clone, Profiles), enhanced existing examples with documentation links, thumbnails, and GitHub links, updated group titles for brevity |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| { | ||
| "slug": "steel-perplexity-clone", | ||
| "id": "steel-perplexity-clone", | ||
| "title": "Build a Perplexity‑style Search Engine", |
There was a problem hiding this comment.
The title uses a non-breaking hyphen (‑) character instead of a standard hyphen (-). This should be a regular hyphen for consistency with the rest of the codebase.
| "title": "Build a Perplexity‑style Search Engine", | |
| "title": "Build a Perplexity-style Search Engine", |
| { | ||
| "id": "oai-computer-use", | ||
| "title": "Using Steel with OpenAI's Computer Use API", | ||
| "title": "OpenAIs Computer Use", |
There was a problem hiding this comment.
The title contains a possessive apostrophe issue. "OpenAIs Computer Use" should be "OpenAI's Computer Use" to properly indicate possession.
| "title": "OpenAIs Computer Use", | |
| "title": "OpenAI's Computer Use", |
| { | ||
| "id": "claude-computer-use", | ||
| "title": "Using Steel with Claude's Computer Use API", | ||
| "title": "Claudes Computer Use", |
There was a problem hiding this comment.
The title contains a possessive apostrophe issue. "Claudes Computer Use" should be "Claude's Computer Use" to properly indicate possession.
| "title": "Claudes Computer Use", | |
| "title": "Claude's Computer Use", |
| ], | ||
| }; | ||
|
|
||
| type EnvVar = {value: string; label: string; required?: boolean}; |
There was a problem hiding this comment.
The EnvVar type is defined after it's used in BASE_ENV and CATEGORY_ENV_MAP declarations. In TypeScript, type definitions should be placed before their first usage to avoid potential issues and improve code readability.
1 participant
No description provided.