
## Problem The mat-icon-button in the actions flow-type section had a shrinking hover background. The hover effect was not displaying properly and appeared constrained. ## Root Cause The margin rules were being applied to all `span` elements, including the Material button's internal elements (like `.mat-mdc-button-label`), which interfered with the button's hover background positioning. ## Solution - Changed the span selector from `span` to `> span` to target only direct children - Added specific margin reset for the button (`margin-right: 0`) - Added margin reset for the icon inside the button - This allows the Material button to use its default hover behavior ## Testing - [x] No visual regressions in text spacing or layout - [x] Button hover background now displays as a proper circle - [x] Other buttons on the page remain unaffected - [x] Matches the behavior of working buttons in trigger sections ## Type of Change - [x] Bug fix (non-breaking change which fixes an UI issue) Before : <img width="427" height="411" alt="Screenshot 2025-07-15 at 6 08 35 PM" src="https://github.com/user-attachments/assets/f728e1fa-6711-4e8b-ba24-2a84329f50d7" /> After fix : <img width="406" height="404" alt="Screenshot 2025-07-15 at 6 09 36 PM" src="https://github.com/user-attachments/assets/27d7b08d-684d-4094-8334-844a4e459025" /> Fixes hover background issue in actions flow-type section. --------- Co-authored-by: Saurabh Thapliyal <saurabh@southguild.tech> Co-authored-by: Marco A. <marco@zitadel.com>
Console Angular App
This is the ZITADEL Console Angular application.
Development
Prerequisites
- Node.js 18 or later
- pnpm (latest)
Installation
pnpm install
Proto Generation
The Console app uses dual proto generation with Turbo dependency management:
@zitadel/proto
generation: Modern ES modules with@bufbuild/protobuf
for v2 APIs- Local
buf.gen.yaml
generation: Traditional protobuf JavaScript classes for v1 APIs
The Console app's turbo.json
ensures that @zitadel/proto#generate
runs before the Console's own generation, providing both:
- Modern schemas from
@zitadel/proto
(e.g.,UserSchema
,DetailsSchema
) - Legacy classes from
src/app/proto/generated
(e.g.,User
,Project
)
Generated files:
@zitadel/proto
: Modern ES modules inlogin/packages/zitadel-proto/
- Local generation: Traditional protobuf files in
src/app/proto/generated/
- TypeScript definition files (
.d.ts
) - JavaScript files (
.js
) - gRPC client files (
*ServiceClientPb.ts
) - OpenAPI/Swagger JSON files (
.swagger.json
)
- TypeScript definition files (
To generate proto files:
pnpm run generate
This automatically runs both generations in the correct order via Turbo dependencies.
Development Server
To start the development server:
pnpm start
This will:
- Fetch the environment configuration from the server
- Serve the app on the default port
Building
To build for production:
pnpm run build
This will:
- Generate proto files (via
prebuild
script) - Build the Angular app with production optimizations
Linting
To run linting and formatting checks:
pnpm run lint
To auto-fix formatting issues:
pnpm run lint:fix
Project Structure
src/app/proto/generated/
- Generated proto files (Angular-specific format)buf.gen.yaml
- Local proto generation configurationturbo.json
- Turbo dependency configuration for proto generationprebuild.development.js
- Development environment configuration script
Proto Generation Details
The Console app uses dual proto generation managed by Turbo dependencies:
Dependency Chain
The Console app has the following build dependencies managed by Turbo:
@zitadel/proto#generate
- Generates modern protobuf files@zitadel/client#build
- Builds the TypeScript gRPC client libraryconsole#generate
- Generates Console-specific protobuf filesconsole#build
- Builds the Angular application
This ensures that the Console always has access to the latest client library and protobuf definitions.
Legacy v1 API (Traditional Protobuf)
- Uses local
buf.gen.yaml
configuration - Generates traditional Google protobuf JavaScript classes extending
jspb.Message
- Uses plugins:
protocolbuffers/js
,grpc/web
,grpc-ecosystem/openapiv2
- Output:
src/app/proto/generated/
- Used for: Most existing Console functionality
Modern v2 API (ES Modules)
- Uses
@zitadel/proto
package generation - Generates modern ES modules with
@bufbuild/protobuf
- Uses plugin:
@bufbuild/es
with ES modules and JSON types - Output:
login/packages/zitadel-proto/
- Used for: New user v2 API and services
Dependency Management
The Console's turbo.json
ensures proper execution order:
@zitadel/proto#generate
runs first (modern ES modules)- Console's local generation runs second (traditional protobuf)
- Build/lint/start tasks depend on both generations being complete
This approach allows the Console app to use both v1 and v2 APIs while maintaining proper build dependencies.
Legacy Information
This project was originally generated with Angular CLI version 8.3.20 and has been updated over time.