typescript: replace widespread ny type usage with proper interfaces in playground components

[piyushdotcomm]

Problem

Multiple components use any types extensively instead of proper TypeScript types. This defeats TypeScript's type safety and makes it harder to catch bugs at compile time.

Instances Found

modules/playground/components/MainPlaygroundPage.tsx

• Line 64: interface MainPlaygroundPageProps { initialData: any; ... } — initialData should be typed as the Playground+TemplateFile shape
• Line 70: rawContent derived from initialData?.templateFiles?.[0]?.content as untyped

modules/playground/components/playground-header.tsx

• Line 25: playgroundData: any;
• Line 28: activeFile: any;

modules/playground/components/collaboration-avatars.tsx

• Line 7: const [users, setUsers] = useState<any[]>([]);

modules/playground/components/ai-chat-panel.tsx

• Line 340: {messages.map((msg: any) => {
• Line 341: const rawParts: any[] = (msg as any).parts ?? [];
• Lines 345, 347, 353: multiple (p: any) usages

modules/playground/components/playground-editor.tsx

• Line 49: const handleEditorDidMount = (editor: any, monaco: Monaco) => {
• Line 61: editor.onDidChangeCursorPosition((e: any) => {

Expected Fix

Define proper interfaces for:

1. PlaygroundData (playground + template files shape from Prisma)
2. ActiveFile (TemplateFile extended with hasUnsavedChanges)
3. CollaboratorUser (name + color shape from Yjs awareness)

Then replace any usage with these typed interfaces.

Why This Matters

• TypeScript errors are already suppressed in builds (ignoreBuildErrors: true) — fixing any types is a prerequisite to safely re-enabling type checking
• any in the message types means AI chat bugs won't be caught by the compiler
• The initialData: any means a malformed server response could crash the playground silently

Files Affected

• modules/playground/components/MainPlaygroundPage.tsx
• modules/playground/components/playground-header.tsx
• modules/playground/components/collaboration-avatars.tsx
• modules/playground/components/ai-chat-panel.tsx
• modules/playground/components/playground-editor.tsx

[github-actions]

👋 Thanks for opening an issue, @piyushdotcomm!

Our maintainers will review this issue shortly 🚀

---

📘 Before Contributing

Please read the contribution guide carefully before requesting assignment:

👉 https://github.com/piyushdotcomm/Editron/blob/main/CONTRIBUTING.md

---

🏷️ NSoC'26 / GSSoC'26 Requirement

Please clearly mention whether you are contributing via:

• NSoC'26
• GSSoC'26
• or as a regular contributor

Example: I am contributing under GSSoC'26

⚠️ Assignment requests without this information may be rejected automatically.

---

⏳ GSSoC Assignment Restriction

GSSoC contributors will only be allowed to take issue assignments after:

🗓️ May 15th, 12:00 AM IST

Before that date, assignment requests from GSSoC contributors will be automatically blocked.

---

🤖 Assignment System

To request assignment, comment: /assign or assign me

The smart assignment workflow validates:

• contributor eligibility
• NSoC/GSSoC participation mention
• active issue assignment limits
• repository contribution rules

---

⚠️ Important Repository Rules

• Do not start working before assignment
• Maximum 3 active assigned issues per contributor
• Contributors are encouraged to combine related fixes into 1–2 quality PRs instead of many small PRs
• PRs without assignment may be closed
• Spam or low-quality PRs may be rejected

Happy contributing 🎉

[Tushar15769]

I would like to work on this issue under GSSoC 2026 so please assign this issue to me @piyushdotcomm .
Thanks!

[github-actions]

⚠️ Maintainer Ping Warning

Hi @Tushar15769,

Please avoid repeatedly pinging maintainers for assignment, review, or merge requests.

Reviews and assignments are handled in queue order. Excessive pinging may lead to spam labeling and restrictions.

Recommended wait times:

• Assignment: 12–24 hours
• Review: 24–72 hours

[srinidhi-2006-bit]

Hi @piyushdotcomm

I’m a GSSoC’26 Contributor/Mentee and I would like to work on this issue.

I understand that the task involves improving type safety across multiple playground components by replacing widespread any usage with proper TypeScript interfaces and typed structures. This includes defining interfaces such as PlaygroundData, ActiveFile, and CollaboratorUser, and updating component props, state values, and callback parameters accordingly.

I’ll make sure the typings remain clean, maintainable, and consistent with the existing project architecture while preserving current functionality.

Please assign this issue to me under GSSoC’26. Looking forward to contributing to Editron

[github-actions]

⚠️ Maintainer Ping Warning

Hi @srinidhi-2006-bit,

Please avoid repeatedly pinging maintainers for assignment, review, or merge requests.

Reviews and assignments are handled in queue order. Excessive pinging may lead to spam labeling and restrictions.

Recommended wait times:

• Assignment: 12–24 hours
• Review: 24–72 hours

[tech-dipesh]

/assign

[github-actions]

❌ Please specify the program:

• /assign gssoc
• /assign nsoc

[Samiksha22911]

Hi @piyushdotcomm , I would like to work on this issue under Gssoc26.

[github-actions]

⚠️ Maintainer Ping Warning

Hi @Samiksha22911,

Please avoid repeatedly pinging maintainers for assignment, review, or merge requests.

Reviews and assignments are handled in queue order. Excessive pinging may lead to spam labeling and restrictions.

Recommended wait times:

• Assignment: 12–24 hours
• Review: 24–72 hours

[piyushdotcomm]

@Samiksha22911 assigned it to you. dont forget to star the repo. and to get assigned automatically from next time read the github bot comment