<aside> 🧭 NAVIGATION

🎯 Problem Statement

🧑🏻‍⚖️ Judging Criteria

💻 Submission Requirements

🏆 Prizes

📚 Resources

🤝 Q&A with the Organizers

</aside>

<aside> ✅ Getting Started

🧩 Hacker Checklist

❓ FAQs

</aside>

<aside> 🔗 Community Channel and Links

🔮 Discourse

</aside>

🔙 Back to Home Page

Snap-in Production Readiness Checklist

Manifest.yaml

• Version is valid and non-deprecated

• Name clearly indicates snap-in purpose and is unique

• Description is clear, concise (~120 chars), and accurate

• Service account usage is justified and properly named

• Event sources:

• [ ] No unnecessary duplicates

• [ ] All configured events are used

• [ ] Filters are added for event sources to only receive events actually needed.

• [ ] No hardcoded secrets

• Globals:

• [ ] All globals are necessary

• [ ] Clear names and descriptions

• [ ] Appropriate types and defaults

• [ ] Configurable tags/messages/timeouts

Code Quality

• Using official DevRev TypeScript SDK

• Using official third-party SDKs where applicable

• Common code is in separate folder

• Error handling:

• [ ] Proper logging with context

• [ ] User-friendly error messages

• [ ] Sufficient retrying on critical calls

• [ ] Response status checks

• Function completion within 2-minute timeout

• Code is formatted and documented

• No unused/commented code

Package.json

• Dependencies are valid and listed
• Dependencies are well-maintained
• development dependencies are listed as such and not a part of dependencies.[ improve the language]
• No malicious dependencies
• Build/test/pack tasks defined

Documentation

• Clear README explaining functionality
• Usage illustrations/videos included
• Known caveats listed
• Clean folder structure

Automations

• Accurate naming
• Proper event type filtering
• Custom events handled

Commands

• Lightweight execution
• Clear naming and descriptions
• No UI blocking operations