AI editor project rules #58

avni-7span · 2025-07-16T09:52:38Z

Description

Added project rules for cursor, windsurf and trae.

Type of Change

✨ New feature (non-breaking change which adds functionality)
🛠️ Bug fix (non-breaking change which fixes an issue)
❌ Breaking change (fix or feature that would cause existing functionality to change)
🧹 Code refactor
✅ Build configuration change
📝 Documentation
🗑️ Chore

Summary by CodeRabbit

New Features
- Added "Forgot Password" and "Verify OTP" flows with new screens, bloc state management, and API integration.
- Introduced OTP input and countdown timer widgets to enhance authentication UX.
- Added new authentication API endpoints and request models for password reset and OTP verification.
- Expanded English translations to support password reset and OTP workflows.
Enhancements
- Updated navigation to include new authentication routes.
- Replaced default app bars with custom app bars across multiple screens for consistent UI.
- Enhanced text field widget with read-only and max length options.
Documentation
- Added extensive project rules and best practices covering Flutter asset management, UI design patterns, navigation, state management, and coding style.
Bug Fixes / Refactor / Style
- Refactored widget formatting and code style for improved readability without changing functionality.

…Scope to avoid conflicts with auto_route

…tency

…ckage and remove unused translation patterns

- Added try-catch to handle error in Remote Config initialisation. - Added 'force_update' key and assigned JSON value to it while set up initial default values, to match Firebase's variable configuration.

This commit introduces the following changes: - Added a forgot password feature, allowing users to reset their passwords. - Implemented a verify OTP (One-Time Password) screen for enhanced security. - Updated the authentication repository to include methods for forgot password and OTP verification. - Added relevant translations for the new features. - Integrated the forgot password flow into the sign-in screen. - Updated API endpoints for forgot password and OTP verification. - Added necessary dependencies, including `pinput` for OTP input.

- Updated ForgotPasswordBloc to handle success and failure cases. - Included errorMessage in ForgotPasswordState props. - Added static OTP validation in VerifyOTPScreen. - Updated VerifyOTPState and VerifyOTPEvent to include props for better state management and event handling. - Removed skeletonizer dependency override from widgetbook.

- Updated API endpoints for forgot password and verify OTP. - Set email field to read-only on the verify OTP screen. - Removed unused `Countdown` widget. - Standardized OTP length to 6 digits in `VerifyOTPBloc`. - Added `readOnly` property to `AppTextField` widget.

Incremented the counter to 2.

This commit introduces a new `AppTimer` widget and integrates it into the OTP verification screen. Key changes: - Added `AppTimer` widget to `app_ui` for displaying a countdown timer. - Integrated `AppTimer` into `VerifyOTPScreen` to show the OTP resend countdown. - Refactored `VerifyOTPScreen` to use `AppTimer` and removed manual timer logic. - Updated `VerifyOTPBloc` to use `LengthValidator` for OTP validation. - Modified navigation from `ForgotPasswordScreen` to `VerifyOTPScreen` to use `replaceRoute` instead of `pushRoute`. - Ensured OTP input is cleared and focus is removed when resending OTP. - Displayed error messages using `SnackbarType.failed` for invalid OTP. - Updated Pinput widget to show error text based on `state.otp.error`. - Allowed only digits in OTP input using `FilteringTextInputFormatter.digitsOnly`.

- Removed unused `formKey` from `VerifyOTPScreen`. - Simplified `AppTimer` widget by removing `onTick` and `textStyle` parameters. - Updated `VerifyOTPState`'s `isValid` getter to include email validation.

The `AppTimer` widget was modified to prevent the timer from starting if the initial `seconds` value is 0. Additionally, the `onFinished` callback is now always called when the timer finishes, even if it's null.

The `AppTimer` widget now correctly formats the remaining time to show both minutes and seconds (MM:SS) instead of just seconds.

- Added `pin_incorrect` localization. - Made `VerifyOTPEvent` subclasses final. - Added assertion for non-negative seconds in `AppTimer`. - Used localized error message for incorrect PIN in `VerifyOTPScreen`.

- Modified `VerifyOTPBloc` to initialize email via `SetEmailEvent` instead of constructor. - Renamed API status fields in `VerifyOTPState` for clarity (e.g., `statusForResendOTP` to `resendOtpStatus`). - Removed redundant `BlocBuilder` widgets in `VerifyOTPScreen`. - Trimmed email input in `ForgotPasswordBloc` before validation and submission. - Changed `AuthRepository.forgotPassword` return type from `TaskEither<Failure, void>` to `TaskEither<Failure, Unit>`. - Replaced `SingleChildScrollView` with `ListView` in `ForgotPasswordScreen` and removed `AutofillGroup`.

Moved the `email` property declaration after the constructor in `SetEmailEvent` for consistency with other event classes.

- Made `emailAddress` a required parameter in `VerifyOTPScreen`. - Removed local timer management from `VerifyOTPScreen` and moved timer logic to `VerifyOTPBloc`. - Simplified OTP verification logic in `VerifyOTPScreen` and `VerifyOTPBloc` to use a static OTP for now. - Replaced `SingleChildScrollView` with `ListView` in `VerifyOTPScreen`. - Updated `VerifyOTPState` to include `isTimerRunning` and changed `email` type to `String`. - Added `StartTimerEvent` and `TimerFinishedEvent` to `VerifyOTPEvent`. - Updated `VerifyOTPBloc` to handle new timer events and use the string email. - Renamed `readOnly` to `isReadOnly` in `AppTextField`.

The padding for the "Verify OTP" button on the `VerifyOTPScreen` has been updated.

Removed the `Padding` widget that was wrapping the `BlocConsumer` in the `VerifyOTPScreen` and moved the padding to the `ListView` instead.

- Added `pinput` dependency to `app_ui/pubspec.yaml`. - Removed `pinput` dependency from `app_core/pubspec.yaml`. - Created `AppOtpInput` widget in `app_ui` to encapsulate OTP input logic. - Replaced direct usage of `Pinput` with `AppOtpInput` in `VerifyOTPScreen`. - Updated various dependency versions in `widgetbook/pubspec.lock`. - Updated Flutter SDK constraint in `widgetbook/pubspec.lock`.

…r fvm can run the command

coderabbitai · 2025-07-16T09:52:45Z

Walkthrough

This update introduces comprehensive project-wide documentation and rule files defining strict standards for Flutter development, including architecture, asset management, UI patterns, navigation, state management, API integration, color usage, and coding style. The rules enforce consistency, type safety, and best practices across all major aspects of the codebase, with detailed guides and migration instructions.

Changes

File(s)	Change Summary
.cursor/rules/assets-rules.mdc .cursor/rules/atomic-design-rule.mdc .cursor/rules/auto-route.mdc .cursor/rules/bloc.mdc .cursor/rules/color.mdc .cursor/rules/flutter-dart.mdc .cursor/rules/structure.mdc	Added markdown documentation files establishing project rules for: asset management with `flutter_gen`, UI development with Atomic Design, navigation with Auto Route, BLoC state management, color and typography standards, Flutter/Dart coding style, and feature/module folder structure. Each file provides detailed guidelines, code patterns, checklists, and migration instructions.
.trae/rules/project_rules.md	Introduced a comprehensive project rules document consolidating standards for asset usage, UI components, navigation, BLoC, repository patterns, color usage, Dart/Flutter style, and feature structure. Provides step-by-step guides, code samples, and best practices.

Sequence Diagram(s)

sequenceDiagram
  participant Developer
  participant Documentation
  Developer->>Documentation: Reads rules for assets, UI, navigation, BLoC, etc.
  Developer->>Documentation: Follows checklists and migration guides
  Developer->>Codebase: Applies prescribed patterns and conventions
  Documentation-->>Developer: Provides troubleshooting and best practices

Possibly related PRs

Updated app_textfield.dart #55: Adds new optional parameters isReadOnly and maxLength to the AppTextField widget, which directly relates to the rules and documentation around widget customization and standardization.

Suggested labels

documentation

Suggested reviewers

cavin-7span

Poem

In the warren of code, where the widgets all play,
A rabbit with glasses wrote rules for the day.
"No stringly-typed assets! Use structure and flair—
Let BLoC and Auto Route guide you with care.
With color and spacing all tidy and neat,
Our Fluttery burrow is truly elite!"
🐇📚✨

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between fd4c8ca and a6411d4.

📒 Files selected for processing (1)

packages/app_ui/lib/src/widgets/molecules/app_textfield.dart (7 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

packages/app_ui/lib/src/widgets/molecules/app_textfield.dart

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

Review comments: Directly reply to a review comment made by CodeRabbit. Example:
- I pushed a fix in commit <commit_id>, please review it.
- Explain this complex logic.
- Open a follow-up GitHub issue for this discussion.
Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
- @coderabbitai explain this code block.
- @coderabbitai modularize this function.
PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
- @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
- @coderabbitai read src/utils.ts and explain its main purpose.
- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
- @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

@coderabbitai pause to pause the reviews on a PR.
@coderabbitai resume to resume the paused reviews.
@coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
@coderabbitai full review to do a full review from scratch and review all the files again.
@coderabbitai summary to regenerate the summary of the PR.
@coderabbitai generate docstrings to generate docstrings for this PR.
@coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
@coderabbitai resolve resolve all the CodeRabbit review comments.
@coderabbitai configuration to show the current CodeRabbit configuration for the repository.
@coderabbitai help to get help.

Other keywords and placeholders

Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (`.coderabbit.yaml`)

You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
Please see the configuration documentation for more information.
If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

Visit our Documentation for detailed information on how to use CodeRabbit.
Join our Discord Community to get help, request features, and share feedback.
Follow us on X/Twitter for updates and announcements.

coderabbitai

Actionable comments posted: 5

🧹 Nitpick comments (10)

.github/ISSUE_TEMPLATE/bug_report.md (1)
24-32: Sample can’t mutate state inside StatelessWidget

count++ inside a StatelessWidget is a no-op and may confuse reporters. Consider switching the snippet to StatefulWidget or using ValueNotifier so the example actually updates the UI.
-class Home extends StatelessWidget {
-  final count = 0;
+class Home extends StatefulWidget {
+  @override
+  State<Home> createState() => _HomeState();
+}
+
+class _HomeState extends State<Home> {
+  int count = 0;
apps/app_core/lib/modules/forgot_password/bloc/forgot_password_state.dart (1)
11-18: Consider consistent parameter ordering in copyWith method.

For better maintainability, consider ordering the copyWith parameters to match the field declaration order in the constructor.
-ForgotPasswordState copyWith({EmailValidator? email, bool? isValid, FormzSubmissionStatus? status, String? errorMessage}) {
+ForgotPasswordState copyWith({FormzSubmissionStatus? status, EmailValidator? email, bool? isValid, String? errorMessage}) {
  return ForgotPasswordState(
-    email: email ?? this.email,
-    isValid: isValid ?? this.isValid,
    status: status ?? this.status,
+    email: email ?? this.email,
+    isValid: isValid ?? this.isValid,
    errorMessage: errorMessage ?? this.errorMessage,
  );
}
packages/app_ui/lib/src/widgets/molecules/app_timer.dart (1)
37-50: Timer implementation is correct but could be optimized.

The timer logic correctly handles countdown and cancellation. However, consider stopping the timer immediately when reaching zero instead of continuing the periodic calls.
void _startTimer() {
  if (widget.seconds == 0) return;
  _timer?.cancel();
  _timer = Timer.periodic(const Duration(seconds: 1), (timer) {
    if (_secondsRemaining > 0) {
      setState(() {
        _secondsRemaining--;
      });
+      if (_secondsRemaining == 0) {
+        timer.cancel();
+        widget.onFinished?.call();
+      }
    } else {
-      timer.cancel();
-      widget.onFinished?.call();
+      // This branch should never be reached now
    }
  });
}
packages/app_ui/lib/src/widgets/molecules/app_otp_input.dart (1)
7-7: Consider adding validation for length parameter.

While the default length of 6 is appropriate, consider adding validation to prevent invalid values.
-const AppOtpInput({required this.onChanged, this.length = 6, this.errorText, super.key});
+const AppOtpInput({required this.onChanged, this.length = 6, this.errorText, super.key}) 
+  : assert(length > 0, 'Length must be positive');
apps/app_core/lib/modules/auth/repository/auth_repository.dart (1)
123-154: Consider consolidating duplicate request handling patterns.

The forgotPassword and verifyOTP methods follow similar request-response patterns. Consider extracting a common helper method to reduce code duplication.

Here's a potential refactor to reduce duplication:
+  TaskEither<Failure, T> _makeAuthRequest<T>(
+    String path,
+    Map<String, dynamic> body,
+    T Function(Map<String, dynamic>) responseMapper,
+  ) => userApiClient.request(
+    requestType: RequestType.post,
+    path: path,
+    body: body,
+    options: Options(headers: {'Content-Type': 'application/json'}),
+  ).chainEither(RepositoryUtils.checkStatusCode)
+   .chainEither((response) => RepositoryUtils.mapToModel(() => responseMapper(response.data as Map<String, dynamic>)));

  @override
  TaskEither<Failure, Unit> forgotPassword(AuthRequestModel authRequestModel) => 
-    makeForgotPasswordRequest(authRequestModel)
-      .chainEither(RepositoryUtils.checkStatusCode)
-      .chainEither((response) => RepositoryUtils.mapToModel(() => response.data))
-      .map((_) => unit);
+    _makeAuthRequest(
+      ApiEndpoints.forgotPassword,
+      authRequestModel.toForgotPasswordMap(),
+      (_) => unit,
+    );

  @override
  TaskEither<Failure, AuthResponseModel> verifyOTP(AuthRequestModel authRequestModel) => 
-    makeVerifyOTPRequest(authRequestModel)
-      .chainEither(RepositoryUtils.checkStatusCode)
-      .chainEither((response) => RepositoryUtils.mapToModel(() => AuthResponseModel.fromMap(response.data as Map<String, dynamic>)));
+    _makeAuthRequest(
+      ApiEndpoints.verifyOTP,
+      authRequestModel.toVerifyOTPMap(),
+      AuthResponseModel.fromMap,
+    );
apps/app_core/lib/modules/verify_otp/bloc/verify_otp_event.dart (1)
33-47: Consider using final keyword for consistency.

The SetEmailEvent, StartTimerEvent, and TimerFinishedEvent classes use class instead of final class. For consistency with other events in the file, consider using final class.
-class SetEmailEvent extends VerifyOTPEvent {
+final class SetEmailEvent extends VerifyOTPEvent {
   const SetEmailEvent(this.email);
   final String email;

   @override
   List<Object> get props => [email];
 }

-class StartTimerEvent extends VerifyOTPEvent {
+final class StartTimerEvent extends VerifyOTPEvent {
   const StartTimerEvent();
 }

-class TimerFinishedEvent extends VerifyOTPEvent {
+final class TimerFinishedEvent extends VerifyOTPEvent {
   const TimerFinishedEvent();
 }
apps/app_core/lib/modules/verify_otp/bloc/verify_otp_bloc.dart (1)
36-37: Document hardcoded OTP for development testing.

Based on the retrieved learning, the team uses static OTP validation for testing. Consider adding a comment explaining this is for development purposes and should be replaced with actual API integration.
  // Static OTP check for now
+ // TODO: Replace with actual API call to verifyOTP when backend is ready
+ // Using hardcoded value "222222" for development testing
  if (state.otp.value == '222222') {
.trae/rules/project_rules.md (3)
1-16: Resolve repeated “## Overview” headings

## Overview appears at least four times. Markdown-lint (MD024) flags this, and duplicated anchors break in-page linking.

Either:

Promote the later instances to a deeper level (###) to reflect their local scope, or

Replace the text with section-specific titles (e.g. “## Asset Management – Overview”, “## Atomic Design – Overview”).

This keeps the document navigable and avoids anchor collisions.

Also applies to: 221-224, 759-762

32-45: Add language identifiers to fenced blocks (MD040)

Several code fences omit a language tag, hurting syntax highlighting & tooling:
-``` 
+```text
   app_ui/
   └── assets/
Apply an appropriate tag (text, bash, yaml, etc.) to all unlabeled fences – notably the directory-tree examples around lines 32-45 and 1357-1370.

Also applies to: 1357-1370

322-347: Use proper heading levels instead of italic-bold pseudo-headings (MD036)

Examples such as ### Spacing Rules are introduced with italic markers (**❌ NEVER …** / **✅ ALWAYS …**) rather than real headings, making the hierarchy inconsistent and harder to scan.

Convert these to true headings:
-### 🛰️ Atoms (Basic Building Blocks)
+#### 🛰️ Atoms (Basic Building Blocks)
Then keep the admonition bullets underneath.
This satisfies markdown-lint and improves accessibility for screen readers.

Also applies to: 370-387, 385-417

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1809f68 and fd4c8ca.

⛔ Files ignored due to path filters (1)

packages/widgetbook/pubspec.lock is excluded by !**/*.lock

📒 Files selected for processing (43)

.cursor/rules/assets-rules.mdc (1 hunks)
.cursor/rules/atomic-design-rule.mdc (1 hunks)
.cursor/rules/auto-route.mdc (1 hunks)
.cursor/rules/bloc.mdc (1 hunks)
.cursor/rules/color.mdc (1 hunks)
.cursor/rules/flutter-dart.mdc (1 hunks)
.cursor/rules/structure.mdc (1 hunks)
.github/ISSUE_TEMPLATE/bug_report.md (1 hunks)
.trae/rules/project_rules.md (1 hunks)
BOILERPLATE/COUNTER (1 hunks)
apps/app_core/lib/app/config/api_endpoints.dart (1 hunks)
apps/app_core/lib/app/routes/app_router.dart (3 hunks)
apps/app_core/lib/core/data/services/firebase_remote_config_service.dart (2 hunks)
apps/app_core/lib/modules/auth/model/auth_request_model.dart (4 hunks)
apps/app_core/lib/modules/auth/repository/auth_repository.dart (5 hunks)
apps/app_core/lib/modules/auth/sign_in/screens/sign_in_screen.dart (5 hunks)
apps/app_core/lib/modules/auth/sign_up/screens/sign_up_screen.dart (1 hunks)
apps/app_core/lib/modules/change_password/screen/change_password_screen.dart (5 hunks)
apps/app_core/lib/modules/forgot_password/bloc/forgot_password_bloc.dart (1 hunks)
apps/app_core/lib/modules/forgot_password/bloc/forgot_password_event.dart (1 hunks)
apps/app_core/lib/modules/forgot_password/bloc/forgot_password_state.dart (1 hunks)
apps/app_core/lib/modules/forgot_password/screens/forgot_password_screen.dart (1 hunks)
apps/app_core/lib/modules/home/screen/home_screen.dart (5 hunks)
apps/app_core/lib/modules/profile/screen/edit_profile_screen.dart (3 hunks)
apps/app_core/lib/modules/subscription/screen/subscription_screen.dart (1 hunks)
apps/app_core/lib/modules/verify_otp/bloc/verify_otp_bloc.dart (1 hunks)
apps/app_core/lib/modules/verify_otp/bloc/verify_otp_event.dart (1 hunks)
apps/app_core/lib/modules/verify_otp/bloc/verify_otp_state.dart (1 hunks)
apps/app_core/lib/modules/verify_otp/screens/verify_otp_screen.dart (1 hunks)
apps/app_core/pubspec.yaml (2 hunks)
melos.yaml (1 hunks)
packages/app_translations/assets/i18n/en.i18n.json (1 hunks)
packages/app_ui/lib/src/widgets/molecules/app_otp_input.dart (1 hunks)
packages/app_ui/lib/src/widgets/molecules/app_textfield.dart (7 hunks)
packages/app_ui/lib/src/widgets/molecules/app_timer.dart (1 hunks)
packages/app_ui/lib/src/widgets/molecules/molecules.dart (1 hunks)
packages/app_ui/pubspec.yaml (1 hunks)
packages/widgetbook/lib/widgets/atoms/app_border_radius.dart (3 hunks)
packages/widgetbook/lib/widgets/atoms/app_text.dart (3 hunks)
packages/widgetbook/lib/widgets/atoms/padding.dart (2 hunks)
packages/widgetbook/lib/widgets/atoms/spacing.dart (3 hunks)
packages/widgetbook/lib/widgets/organisms/app_scaffold.dart (1 hunks)
packages/widgetbook/pubspec_overrides.yaml (1 hunks)

🧰 Additional context used

🧠 Learnings (12)

packages/app_ui/lib/src/widgets/molecules/molecules.dart (1)

Learnt from: tulsi-7span
PR: 7span/dashing-kit#56
File: apps/app_core/lib/modules/verify_otp/screens/verify_otp_screen.dart:98-112
Timestamp: 2025-06-26T11:54:23.406Z
Learning: In the verify OTP screen (apps/app_core/lib/modules/verify_otp/screens/verify_otp_screen.dart), the team uses static OTP validation with hardcoded value "222222" for testing success states during development, rather than calling the actual API verification.

apps/app_core/lib/app/routes/app_router.dart (1)

Learnt from: tulsi-7span
PR: 7span/dashing-kit#56
File: apps/app_core/lib/modules/verify_otp/screens/verify_otp_screen.dart:98-112
Timestamp: 2025-06-26T11:54:23.406Z
Learning: In the verify OTP screen (apps/app_core/lib/modules/verify_otp/screens/verify_otp_screen.dart), the team uses static OTP validation with hardcoded value "222222" for testing success states during development, rather than calling the actual API verification.

apps/app_core/lib/app/config/api_endpoints.dart (1)

Learnt from: tulsi-7span
PR: 7span/dashing-kit#56
File: apps/app_core/lib/modules/verify_otp/screens/verify_otp_screen.dart:98-112
Timestamp: 2025-06-26T11:54:23.406Z
Learning: In the verify OTP screen (apps/app_core/lib/modules/verify_otp/screens/verify_otp_screen.dart), the team uses static OTP validation with hardcoded value "222222" for testing success states during development, rather than calling the actual API verification.

apps/app_core/lib/modules/change_password/screen/change_password_screen.dart (1)

Learnt from: tulsi-7span
PR: 7span/dashing-kit#56
File: apps/app_core/lib/modules/verify_otp/screens/verify_otp_screen.dart:98-112
Timestamp: 2025-06-26T11:54:23.406Z
Learning: In the verify OTP screen (apps/app_core/lib/modules/verify_otp/screens/verify_otp_screen.dart), the team uses static OTP validation with hardcoded value "222222" for testing success states during development, rather than calling the actual API verification.

apps/app_core/lib/modules/verify_otp/bloc/verify_otp_state.dart (1)

Learnt from: tulsi-7span
PR: 7span/dashing-kit#56
File: apps/app_core/lib/modules/verify_otp/screens/verify_otp_screen.dart:98-112
Timestamp: 2025-06-26T11:54:23.406Z
Learning: In the verify OTP screen (apps/app_core/lib/modules/verify_otp/screens/verify_otp_screen.dart), the team uses static OTP validation with hardcoded value "222222" for testing success states during development, rather than calling the actual API verification.

packages/app_ui/lib/src/widgets/molecules/app_otp_input.dart (1)

Learnt from: tulsi-7span
PR: 7span/dashing-kit#56
File: apps/app_core/lib/modules/verify_otp/screens/verify_otp_screen.dart:98-112
Timestamp: 2025-06-26T11:54:23.406Z
Learning: In the verify OTP screen (apps/app_core/lib/modules/verify_otp/screens/verify_otp_screen.dart), the team uses static OTP validation with hardcoded value "222222" for testing success states during development, rather than calling the actual API verification.

apps/app_core/lib/modules/forgot_password/screens/forgot_password_screen.dart (1)

Learnt from: tulsi-7span
PR: 7span/dashing-kit#56
File: apps/app_core/lib/modules/verify_otp/screens/verify_otp_screen.dart:98-112
Timestamp: 2025-06-26T11:54:23.406Z
Learning: In the verify OTP screen (apps/app_core/lib/modules/verify_otp/screens/verify_otp_screen.dart), the team uses static OTP validation with hardcoded value "222222" for testing success states during development, rather than calling the actual API verification.

apps/app_core/lib/modules/auth/model/auth_request_model.dart (1)

Learnt from: tulsi-7span
PR: 7span/dashing-kit#56
File: apps/app_core/lib/modules/verify_otp/screens/verify_otp_screen.dart:98-112
Timestamp: 2025-06-26T11:54:23.406Z
Learning: In the verify OTP screen (apps/app_core/lib/modules/verify_otp/screens/verify_otp_screen.dart), the team uses static OTP validation with hardcoded value "222222" for testing success states during development, rather than calling the actual API verification.

apps/app_core/lib/modules/verify_otp/screens/verify_otp_screen.dart (1)

Learnt from: tulsi-7span
PR: 7span/dashing-kit#56
File: apps/app_core/lib/modules/verify_otp/screens/verify_otp_screen.dart:98-112
Timestamp: 2025-06-26T11:54:23.406Z
Learning: In the verify OTP screen (apps/app_core/lib/modules/verify_otp/screens/verify_otp_screen.dart), the team uses static OTP validation with hardcoded value "222222" for testing success states during development, rather than calling the actual API verification.

apps/app_core/lib/modules/verify_otp/bloc/verify_otp_event.dart (1)

Learnt from: tulsi-7span
PR: 7span/dashing-kit#56
File: apps/app_core/lib/modules/verify_otp/screens/verify_otp_screen.dart:98-112
Timestamp: 2025-06-26T11:54:23.406Z
Learning: In the verify OTP screen (apps/app_core/lib/modules/verify_otp/screens/verify_otp_screen.dart), the team uses static OTP validation with hardcoded value "222222" for testing success states during development, rather than calling the actual API verification.

apps/app_core/lib/modules/verify_otp/bloc/verify_otp_bloc.dart (1)

Learnt from: tulsi-7span
PR: 7span/dashing-kit#56
File: apps/app_core/lib/modules/verify_otp/screens/verify_otp_screen.dart:98-112
Timestamp: 2025-06-26T11:54:23.406Z
Learning: In the verify OTP screen (apps/app_core/lib/modules/verify_otp/screens/verify_otp_screen.dart), the team uses static OTP validation with hardcoded value "222222" for testing success states during development, rather than calling the actual API verification.

apps/app_core/lib/modules/auth/repository/auth_repository.dart (1)

Learnt from: tulsi-7span
PR: 7span/dashing-kit#56
File: apps/app_core/lib/modules/verify_otp/screens/verify_otp_screen.dart:98-112
Timestamp: 2025-06-26T11:54:23.406Z
Learning: In the verify OTP screen (apps/app_core/lib/modules/verify_otp/screens/verify_otp_screen.dart), the team uses static OTP validation with hardcoded value "222222" for testing success states during development, rather than calling the actual API verification.

🪛 LanguageTool

.trae/rules/project_rules.md

[style] ~1247-~1247: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...e extensions using UpperCamelCase. 4. Name packages, directories, and source files...