[UXIT-1509] Enable strict mode for ecosystem entries [skip percy]

[CharlyMartin]

📝 Description

This PR updates how we handle Zod validations, starting with ecosystem projects. I prioritized these updates over digest articles because the comms team is now merging PR on their own, so this will be a necessary safety net.

I had to rework our Zod Validations in order to enable strict mode, which throws an error when unrecognized keys are found in the object.

🛠️ Key Changes

• Updated the EcosystemProjectFrontMatter schema - and the schemas it extended - to use kebab-case for property keys, aligning with the data format from the CMS.
• Since the rest of the codebase uses camelCase, I installed the camelcase-keys package (npm) to convert the object keys to standard JavaScript format.

Some code duplication was required to maintain compatibility with the other Zod Schemas:

• BaseDataSchemaKebabCase is a temporary duplicate of DynamicBaseDataSchema
• getMarkdownData is a temporary duplicate of getData

🧪 How to Test

Add an extra field to any ecosystem entry, build the project, and ensure it fails as expected.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
filecoin-foundation-site	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 9, 2024 9:53am

[sentry-io]

🔍 Existing Issues For Review

Your pull request is modifying functions with the following pre-existing issues:

📄 File: src/app/_utils/convertMarkdownToEventData.ts

Function	Unhandled Issue
convertMarkdownToEventData	Error: EventFrontMatterSchema is not defined /eve... Event Count: 1 Affected Users: 1
convertMarkdownToEventData	ReferenceError: EventFrontMatterSchema is not defined Page.generateMetadata (/events/[s... Event Count: 1 Affected Users: 0
convertMarkdownToEventData	ReferenceError: EventFrontMatterSchema is not defined Page Server Component (/events/[s... Event Count: 1 Affected Users: 0

---

_{Did you find this useful? React with a 👍 or 👎}

[notion-workspace]

[FF][BUG] Look into enabling ZOD strict mode for Markdown data

[mirhamasala]

Let's change the data - If I remember correctly, Matt was putting in his own email address for the ones that don't have it.

[CharlyMartin]

Yes good point, let's do that.

[mirhamasala]

@CharlyMartin - Super happy about this! Looking good! I would prefer if we make the email and full-name required and address the data inconsistencies in this PR. Thank you.

[CharlyMartin]

@mirhamasala I added name and full-name to all Markdown entries where they were missing. It was the case for most of them as you can see in the file diff. I used Matt's full name and email as the default.

I used a script to do this, it was a bit tricky due to the encryption step, but it worked :) I checked a handful of files locally via the CMS, and they show the right data.

[mirhamasala]

@CharlyMartin - This is good to go! 🙌🏼🧀 Let's get the other ones sorted too! 🤩

Tag @barbaraperic for visibility~