Skip to content

Organize workspace structure#285

Open
Castro19 wants to merge 2 commits intomainfrom
organize-workspace-structure
Open

Organize workspace structure#285
Castro19 wants to merge 2 commits intomainfrom
organize-workspace-structure

Conversation

@Castro19
Copy link
Copy Markdown
Owner

📌 Summary

Reorganized project structure to follow monorepo best practices by moving client-specific files to their proper locations and maintaining deployment configurations at the root level.

🔍 Related Issues

Closes #N/A (This was a structural improvement)

🛠 Changes Made

  • Moved vite-env.d.ts from root src/ to packages/client/src/

    • This file contains client-specific TypeScript definitions for Vite environment variables
    • It's now properly scoped to the client package where it's used
    • Improves package isolation and maintainability
  • Kept .deployment in root directory

    • This file is used by Azure App Service for deployment configuration
    • Contains SCM_DO_BUILD_DURING_DEPLOYMENT=true setting
    • Affects the entire project's deployment process
  • Kept .gitattributes in root directory

    • Contains Git repository-level configuration
    • Sets * text=auto for consistent line endings across platforms
    • Affects all files in the monorepo

✅ Checklist

  • My code follows the PolyLink Contribution Guidelines.

    • Files are now in their proper locations following monorepo best practices
    • Package-specific files are contained within their respective packages
    • Root-level configuration files remain at the root
  • I have tested my changes to ensure they work as expected.

    • Verified file locations are correct
    • Confirmed TypeScript definitions are accessible to the client package
    • Deployment configurations remain functional
  • I have documented my changes.

    • Added clear explanations for each file's purpose and location
    • Documented the reasoning behind each organizational decision
  • My PR has a clear title and description.

    • Title clearly indicates the structural changes
    • Description provides detailed explanation of each change

📸 Screenshots (if applicable)

N/A (Structural changes don't require visual documentation)

❓ Additional Notes

  • This change improves the project's organization and maintainability
  • No functional changes were made; this is purely a structural improvement
  • The changes align with monorepo best practices and make the codebase more intuitive for new developers
  • All deployment and Git configurations remain intact and functional

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant