feat(schema, api-client): Migrate variable schemas and types to @keyshade/schema

[muntaxir4]

Description

@keyshade/schema

• Add schemas and types for variable.
• Add tests for variable schemas.
• Export variable schemas from index and its types from index.types
• Add InviteMemberRequest and InviteMemberResponse schemas in workspace.
• Create .npmignore to exclude source ts files during installing in an app.

@keyshade/api-client

• Remove existing variable.types.ts.
• Change imports for variable types to @keyshade/schema.
  

Related to #519

Developer's checklist

• My PR follows the style guidelines of this project
• I have performed a self-check on my work

If changes are made in the code:

• I have followed the coding guidelines
• My changes in code generate no new warnings
• My changes are breaking another fix/feature of the project
• I have added test cases to show that my feature works
• I have added relevant screenshots in my PR
• There are no UI/UX issues

Documentation Update

• This PR requires an update to the documentation at docs.keyshade.xyz
• I have made the necessary updates to the documentation, or no documentation changes are required.

[codiumai-pr-agent-free]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

🎫 Ticket compliance analysis ✅ 519 - Fully compliant Compliant requirements: Created variable folder in schema with proper structure Added variable.ts with zod schemas Added variable.types.ts with inferred types Updated api-client to use types from schema Added exports in index files

⏱️ Estimated effort to review: 3 🔵🔵🔵⚪⚪

🧪 PR contains tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Code Smell The RollBackVariableResponseSchema uses string type for count field which should typically be a number for consistency Validation Gap The CreateVariableRequestSchema allows empty arrays for entries which could lead to invalid states

[codiumai-pr-agent-free]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
Possible issue	Add validation to ensure version numbers are positive integers to prevent invalid rollback requests Add validation for the version number to ensure it's a positive integer in the RollBackVariableRequestSchema packages/schema/src/variable/index.ts [78-82] export const RollBackVariableRequestSchema = z.object({ variableSlug: z.string(), - version: z.number(), + version: z.number().int().positive(), environmentSlug: z.string() }) Apply this suggestion Suggestion importance[1-10]: 7 Why: The suggestion adds important validation to prevent invalid version numbers in rollback requests, which could cause runtime errors or unexpected behavior. Using positive integers is a logical constraint for version numbers.	7
General	Add validation to prevent empty workspace IDs in project references Add validation for the project workspaceId to ensure it's a non-empty string in the VariableSchema packages/schema/src/variable/index.ts [13-15] project: z.object({ - workspaceId: z.string() + workspaceId: z.string().min(1) }), Apply this suggestion Suggestion importance[1-10]: 5 Why: Adding minimum length validation for workspaceId helps prevent empty strings, though the base string validation would already catch null/undefined. The impact is moderate as empty strings are an edge case.	5

💡 Need additional feedback ? start a PR chat