Skip to content
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

Fix map marker background color #206

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

kaushiksaliya
Copy link
Collaborator

@kaushiksaliya kaushiksaliya commented Jan 10, 2025

  • Fix map marker background color.
  • Add dark mode state so we can reload the marker list again previously when we change model then marker bg color not change because of marker list is already created we need to rebuild that list same as user selection.
  • Add onPlatformBrightnessChanged in map screen initState this callback is called every time on brightness changes.
Fix.marker.color.webm

Summary by CodeRabbit

  • New Features

    • Enhanced map marker customization with new color parameter
    • Improved dark mode responsiveness for map view
  • Bug Fixes

    • Updated marker generation and styling logic
    • Refined calendar day interaction and visibility rules
  • Refactor

    • Streamlined state management for map view
    • Adjusted color handling for system brightness changes

Copy link

coderabbitai bot commented Jan 10, 2025

Warning

Rate limit exceeded

@kaushiksaliya has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 14 minutes and 43 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between cd6d56c and 70fd128.

📒 Files selected for processing (2)
  • app/lib/ui/flow/home/map/map_view_model.dart (4 hunks)
  • app/lib/ui/flow/home/map/map_view_model.freezed.dart (13 hunks)

Walkthrough

This pull request introduces enhancements to the map and calendar functionality within the application. The changes primarily focus on improving marker generation, map styling, and dark mode responsiveness. A new markerColor parameter is added to marker creation, and the map screen now dynamically adapts to system brightness settings. Additionally, the horizontal calendar view's day interaction logic has been refined to provide more precise control over date selection and visibility.

Changes

File Change Summary
app/lib/ui/flow/home/map/components/marker_generator.dart Added markerColor parameter to createMarkerFromAsset function, modifying marker color logic
app/lib/ui/flow/home/map/map_screen.dart Implemented dynamic map style updates based on system brightness, added brightness change listener
app/lib/ui/flow/home/map/map_view_model.dart Added reloadMarker method and isDarMode state property for managing dark mode
app/lib/ui/flow/home/map/map_view_model.freezed.dart Updated generated code to support isDarMode property in state management
app/lib/ui/flow/journey/calender/horizontal_calendar_view.dart Refined day visibility and interaction logic using groupCreatedDate

Sequence Diagram

sequenceDiagram
    participant User
    participant MapScreen
    participant MapViewModel
    participant MarkerGenerator

    User->>MapScreen: Change system brightness
    MapScreen->>MapViewModel: reloadMarker(isDarkMode)
    MapViewModel-->>MapScreen: Update state
    MapScreen->>MarkerGenerator: createMarkerFromAsset with markerColor
    MarkerGenerator-->>MapScreen: Generate markers
Loading

Possibly Related PRs

Poem

🐰 Markers dance in light and shade,
Dark mode's magic now displayed!
Colors shift with system's might,
Rabbit's map, a coding delight! 🗺️
Brightness changes, markers gleam,
A chromatic, dynamic dream! 🌈


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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.
    • Generate unit testing code for this file.
    • 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 generate unit testing code for this file.
    • @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 generate unit testing code.
    • @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.

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. (Beta)
  • @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.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (2)
app/lib/ui/flow/home/map/map_screen.dart (1)

341-342: Consider using consistent color selection logic.

For better consistency, consider using the same color selection logic as in _observeReloadMarker:

-            context, next.values.toList(), context.colorScheme.textPrimary,
+            context, next.values.toList(), 
+            (state.isDarMode) ? Colors.white : Colors.black,
app/lib/ui/flow/home/map/map_view_model.dart (1)

442-444: Add documentation for the reloadMarker method.

Consider adding documentation to explain the purpose and usage of this method:

+  /// Updates the dark mode state and triggers marker reload
+  /// @param isDarkMode true if dark mode is enabled, false otherwise
   void reloadMarker(bool isDarkMode) {
     state = state.copyWith(isDarMode: isDarkMode);
   }
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 6ac4036 and cd6d56c.

⛔ Files ignored due to path filters (1)
  • app/pubspec.lock is excluded by !**/*.lock
📒 Files selected for processing (5)
  • app/lib/ui/flow/home/map/components/marker_generator.dart (2 hunks)
  • app/lib/ui/flow/home/map/map_screen.dart (4 hunks)
  • app/lib/ui/flow/home/map/map_view_model.dart (4 hunks)
  • app/lib/ui/flow/home/map/map_view_model.freezed.dart (13 hunks)
  • app/lib/ui/flow/journey/calender/horizontal_calendar_view.dart (1 hunks)
🔇 Additional comments (7)
app/lib/ui/flow/home/map/components/marker_generator.dart (1)

15-16: LGTM! Clean implementation of marker color handling.

The addition of the markerColor parameter and the updated color selection logic effectively supports dynamic marker colors while maintaining consistent highlighting for selected markers.

Also applies to: 25-26

app/lib/ui/flow/journey/calender/horizontal_calendar_view.dart (1)

78-80: Review date boundary handling logic.

The introduction of groupCreatedDate by subtracting one day from allowedAfterDate could lead to unexpected behavior around date boundaries. Additionally, this change seems unrelated to the PR's stated objectives of fixing map marker colors and dark mode support.

Could you clarify the reasoning behind this date calculation change? If it's addressing a specific issue, we should add tests to verify the behavior around date boundaries.

app/lib/ui/flow/home/map/map_screen.dart (2)

49-63: LGTM! Well-implemented platform brightness detection.

The initialization and platform brightness change listener are properly implemented, ensuring the map style and markers update correctly when the system theme changes.


305-321: LGTM! Clean implementation of marker reloading.

The _observeReloadMarker method effectively handles marker updates when dark mode changes, with proper cleanup and state management.

app/lib/ui/flow/home/map/map_view_model.dart (2)

465-465: LGTM! Proper state management for dark mode.

The isDarMode state property is correctly initialized and integrated into the state management system.


279-279: LGTM! Improved null safety in showMemberDetail.

The update to use optional chaining improves the null safety of the code.

app/lib/ui/flow/home/map/map_view_model.freezed.dart (1)

Line range hint 1-700: Reminder: Do not modify generated files directly.

This is an auto-generated file by the Freezed package. Any changes should be made in the source file map_view_model.dart instead of modifying this file directly.

Run this script to locate the source file:

✅ Verification successful

Do not modify generated files directly

The file map_view_model.freezed.dart is auto-generated by the Freezed package. Any changes should be made in the source file at app/lib/ui/flow/home/map/map_view_model.dart instead.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Find the source file that generates this freezed file
fd --type f "map_view_model.dart" --exclude "*.freezed.dart" --exclude "*.g.dart"

Length of output: 192

app/lib/ui/flow/home/map/map_view_model.freezed.dart Outdated Show resolved Hide resolved
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