Skip to content

Fix category validation and alphabetical order for Screenshot to Code#1091

Open
rnsss wants to merge 3 commits intomarcelscruz:mainfrom
rnsss:rnsss-patch-1
Open

Fix category validation and alphabetical order for Screenshot to Code#1091
rnsss wants to merge 3 commits intomarcelscruz:mainfrom
rnsss:rnsss-patch-1

Conversation

@rnsss
Copy link
Copy Markdown

@rnsss rnsss commented Mar 31, 2026

Summary

This PR fixes the Screenshot to Code resource entry by updating the categories and placing it in the correct alphabetical position in resources/s.ts.

Changes made

  • Moved Screenshot to Code before Syntax
  • Updated categories to valid repository categories

Updated resource

  • Name: Screenshot to Code
  • URL: https://screenshottocode.net/
  • Description: Tool for converting screenshots and UI mockups into frontend code to accelerate prototyping workflows.
  • Categories: AI, Programming
  • Keywords: screenshot, ui, frontend, prototyping, react, tailwind

Checklist

  • My changes were made in the resources folder, not in the auto-generated README.md file or db folder
  • The resource is highly or exclusively related to programming and development
  • My submission is formatted according to the guidelines in the contributing guide
  • My submission is ordered alphabetically based on the resource name
  • My submission has a useful description
  • I have searched the repository for any relevant issues or pull requests

rnsss added 2 commits March 31, 2026 14:38
Add Screenshot to Code to resources/s.ts as a frontend/AI development tool.
@github-actions
Copy link
Copy Markdown
Contributor

New resource link: https://screenshottocode.net/

@github-actions
Copy link
Copy Markdown
Contributor

🤖 Automated PR Validation

⚠️ Issues Found

The following issues were detected. GitHub Copilot will review this PR and report any additional issues.

Resource Validation Errors

🔤 Alphabetical Order

  • a.ts:455: Resource "All SVG Icons" should come before "Azure"
  • l.ts:456: Resource "LargeMI" should come before "Luthor"
  • n.ts:38: Resource "NAT Checker" should come before "NativeBridge"
  • s.ts:1047: Resource "Screenshot to Code" should come before "Swetrix"
  • t.ts:556: Resource "TypersWorld" should come before "TypingClub"

📊 Too Many Categories

  • s.ts:458: Resource "SlingSite": Has 8 categories (max 3)

📋 Request for GitHub Copilot

Review this PR and report any issues you find, including:

  • Code quality and style issues
  • Additional validation errors not caught by automated checks
  • Best practices and improvements

📚 Resources:

GitHub Copilot will review this PR and report any issues found.

@github-actions
Copy link
Copy Markdown
Contributor

New resource link: https://screenshottocode.net/

@github-actions
Copy link
Copy Markdown
Contributor

🤖 Automated PR Validation

⚠️ Issues Found

The following issues were detected. GitHub Copilot will review this PR and report any additional issues.

Resource Validation Errors

🔤 Alphabetical Order

  • a.ts:455: Resource "All SVG Icons" should come before "Azure"
  • l.ts:456: Resource "LargeMI" should come before "Luthor"
  • n.ts:38: Resource "NAT Checker" should come before "NativeBridge"
  • t.ts:556: Resource "TypersWorld" should come before "TypingClub"

📊 Too Many Categories

  • s.ts:465: Resource "SlingSite": Has 8 categories (max 3)

📋 Request for GitHub Copilot

Review this PR and report any issues you find, including:

  • Code quality and style issues
  • Additional validation errors not caught by automated checks
  • Best practices and improvements

📚 Resources:

GitHub Copilot will review this PR and report any issues found.

@rnsss
Copy link
Copy Markdown
Author

rnsss commented Mar 31, 2026

Thanks — I fixed the Screenshot to Code entry and the remaining validation warnings appear to be unrelated pre-existing issues. Happy to make any further adjustments if needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant