feat: Added zod schema

[realAbhi-web]

What does this PR do?

Added Zod Schema to validate and parse app metadata stored in config.json to ensure consistency and better error handling.

-GitHub issue number - #14808

• Fixes CAL-3584

Mandatory Tasks (DO NOT REMOVE)

• I have self-reviewed the code (A decent size PR without self-review might be rejected).

• yes

• I have updated the developer docs in /docs if this PR makes changes that would require a documentation change. If N/A, write N/A here and check the checkbox.

• no

• I confirm automated tests are in place that prove my fix is effective or that my feature works.

• yes

How should this be tested?

The schema should validate the config.json and pass without errors if the metadata is correct.

• Are there environment variables that should be set?
  no

Checklist

• I haven't read the contributing guide
  yes

• My code doesn't follow the style guidelines of this project
  no

• I haven't commented my code, particularly in hard-to-understand areas
  yes

• I haven't checked if my changes generate no new warnings
  yes

[vercel]

@realAbhi-web is attempting to deploy a commit to the cal Team on Vercel.

A member of the Team first needs to authorize it.

[CLAassistant]

All committers have signed the CLA.

[github-actions]

Hey there and thank you for opening this pull request! 👋🏼

We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.

Details:

No release type found in pull request title "Zod Schema feat. done". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit

[graphite-app]

Graphite Automations

"Add consumer team as reviewer" took an action on this PR • (11/17/24)

1 reviewer was added to this PR based on Keith Williams's automation.

"Add foundation team as reviewer" took an action on this PR • (11/17/24)

1 reviewer was added to this PR based on Keith Williams's automation.

"Add community label" took an action on this PR • (11/17/24)

1 label was added to this PR based on Keith Williams's automation.

[keithwillcode]

@hariombalhara Can you please take a look at this one?

[hariombalhara]

@realAbhi-web Thanks for the PR 🙏

Could you take a look at this comment and see if it would improve things and is doable or not?

#14997 (comment)

[realAbhi-web]

i looked at your comment, i didn't completly grasp the idea of what you were guiding for can you explain in detail, I will try my best but still i am a newbie

[hariombalhara]

Hey, so the requirement is to have type safety for config.json. We could do it in 2 ways I believe

• Parse each config.json through zod schema which adds runtime cost which keeps on increasing as more apps are added.
• Instead of using config.json directly we generate a ts file from it and use that instead.So, the code never imports config.json when using an app. We will commit the generated files. We do similar file generation in build file linked in the comment. We could use zod at compile time this way before generating the ts files.

[zomars]

Closing this PR since is not the meeting our current requirements. Feel free re-open once feedback is addressed. 🙏