Skip to content

[GSSoC26] chore: Add admin to lint-staged and create admin .env.example#437

Open
ashrion wants to merge 1 commit into
Nsanjayboruds:mainfrom
ashrion:feat/admin-lint-staged-env
Open

[GSSoC26] chore: Add admin to lint-staged and create admin .env.example#437
ashrion wants to merge 1 commit into
Nsanjayboruds:mainfrom
ashrion:feat/admin-lint-staged-env

Conversation

@ashrion

@ashrion ashrion commented Jul 11, 2026

Copy link
Copy Markdown

Description\nThis PR adds admin app to the root lint-staged configuration and creates an admin .env.example file.\n\n## Changes\n- Added �dmin/**/*.{js,jsx} to lint-staged config in root package.json for ESLint auto-fix\n- Created �dmin/.env.example with VITE_SERVER_URL and VITE_BACKEND_URL variables\n\n## Motivation\n- Admin app was missing from lint-staged configuration, so ESLint fixes weren't auto-applied on commit\n- Admin app uses VITE_SERVER_URL / VITE_BACKEND_URL but had no .env.example documentation\n- Consistent developer experience across all three apps (frontend, backend, admin)\n\n## Testing\n- Run

pm run format from root - verify admin files are formatted\n- Stage admin JS/JSX files and commit - verify lint:fix runs\n\nCloses #436\n\nGSSoC26 contribution

- Add admin/**/*.{js,jsx} to lint-staged configuration for ESLint auto-fix
- Create admin/.env.example with VITE_SERVER_URL and VITE_BACKEND_URL variables
- Referenced in AdminProvider for backend API connection

GSSoC26
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