-
Notifications
You must be signed in to change notification settings - Fork 0
Feature/part7 #54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Feature/part7 #54
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…lication and LLMs files
…ved compatibility
…ESLint rules for boundaries enforcement
…ESLint rules for boundaries enforcement
…abel' to 'web-label' and 'app-post-card' to 'web-post-card'
…nd consistency, add login component and styles, and update routing logic
…ate styles for consistency, and improve responsiveness
…or tag selection, search functionality, and dropdown menu
…rity, adjust router links, and implement new layout component
…ve spacing, and update component structure for better layout consistency
…istency and clarity across components
…or consistency and clarity across components
…e generation from Supabase posts and adjust Angular SSR configuration
…egister components for consistency, adjust template syntax, and improve import paths
…ling, and improve button positioning for better responsiveness
…e module allowance rules for improved structure and clarity
…m shared module for consistency and clarity across components
…rom shared module and enhance public API structure for improved clarity and maintainability
…nhance rules for clarity and safety, and utilize optional chaining for better null handling
…lement DestroyRef cleanup for event listeners and MutationObserver, convert @input to signal inputs, and standardize error handling for improved clarity and maintainability
…es to provide more context and ensure type safety for error handling
…kup and enhance structure for better maintainability
…component creation and enhance code structure for better maintainability
…ns and specify file patterns for improved code quality
…nvironment.ts to ensure correct file structure in CI workflow
…compatibility with latest features
…d actions to v4 for improved performance and compatibility
… tests for improved routing and performance
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request introduces a major refactor to support a multi-project Angular workspace architecture, including new configuration files, project separation, and updated build/deployment workflows. The changes enable modular development with distinct apps for admin, web, code samples micro-frontend, and shared libraries, aligning with modern Angular best practices and deployment targets.
Workspace & Project Structure
angular.json, defining separate projects foradmin,web,code-samples-mfe, andshared, each with their own build, serve, test, and lint configurations. This enables modular development and easier maintenance. [1] [2]Build & Deployment Configuration
Dockerfilefor SSR deployment of the blog app on Google Cloud Run, using a multi-stage build process and supporting bothpnpmandnpmfor dependency installation..github/workflows/google-cloudrun-docker.ymlto use new build and test commands (npm run test:all,npm run build web --configuration production) for compatibility with the new workspace structure. [1] [2]Development & Formatting Standards
.prettierrcfile to standardize code formatting across the workspace, including overrides for HTML, SCSS, and Markdown files.Hosting & Environment Configuration
.firebasercto define Firebase Hosting targets for admin and samples sites, supporting multi-app deployment.Documentation & Guidelines
CLAUDE.mdwith detailed guidance for LLM-assisted development, outlining project architecture, coding standards, migration status, and authoritative context files for future refactoring and code changes.