Update Flowing Code's logo and coordinates on demo

[paodb]

Close #164

Summary by CodeRabbit

• Style
  • Updated the Google Maps demo marker icon to a new 2025 image, improving visual clarity and consistency across demos.
• Tests
  • Adjusted the demo map’s initial center to a nearby location for a more relevant default view on load.
  • Ensured both demo samples reflect the new center and icon, providing a consistent experience during trials.
  • No changes to public APIs or user workflows; updates are purely visual and demo-focused.

[coderabbitai]

Walkthrough

Updated demo map center coordinates and replaced marker icon URLs in two test/demo classes under com.flowingcode.vaadin.addons.googlemaps. No public APIs changed.

Changes

Cohort / File(s)	Summary
Demo map and marker updates src/test/java/.../googlemaps/CustomizedMarkerIconsDemo.java, src/test/java/.../googlemaps/GoogleMapsDemo.java	Changed map center LatLon to -31.620173186615883, -60.67964404821396. Updated marker icon URL from 2020/06/FCMarker.png to 2025/09/marker_1.png.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Suggested reviewers

• mlopezFC
• javier-godoy

Pre-merge checks and finishing touches

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Out of Scope Changes Check	⚠️ Warning	In addition to the logo update, the PR modifies the demo map center coordinates in GoogleMapsDemo.java and CustomizedMarkerIconsDemo.java (previous centers were changed to LatLon(-31.620173186615883, -60.67964404821396)), and those coordinate changes are not referenced in linked issue [#164], so they appear to be out-of-scope. Because the coordinate updates alter demo behavior and were not documented or justified in the issue or PR description, this constitutes an out-of-scope modification that requires clarification.	Either remove the coordinate changes from this PR and submit them as a separate PR, or update this PR description and the linked issue to explicitly include and justify the coordinate updates; if retained, add a brief rationale in the PR body and list the affected demo files (GoogleMapsDemo.java and CustomizedMarkerIconsDemo.java).
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title "Update Flowing Code's logo and coordinates on demo" succinctly and accurately summarizes the main changes in this PR—replacing the FlowingCode marker/logo and updating demo map coordinates—and is concise and specific enough for a reviewer scanning history to understand the primary intent.
Linked Issues Check	✅ Passed	Linked issue [#164] requests updating the FlowingCode logo in the demo; this PR replaces the FCMarker.png URL with marker_1.png in GoogleMapsDemo.java and CustomizedMarkerIconsDemo.java and includes "Close #164" in the description, so the primary coding objective of the linked issue is satisfied. The issue provided no additional constraints, and the logo change is applied consistently across the demo files referenced.

✨ Finishing touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch issue-164

---

📜 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 b345c34 and 987b693.

📒 Files selected for processing (2)

• src/test/java/com/flowingcode/vaadin/addons/googlemaps/CustomizedMarkerIconsDemo.java (1 hunks)
• src/test/java/com/flowingcode/vaadin/addons/googlemaps/GoogleMapsDemo.java (2 hunks)

🔇 Additional comments (5)

src/test/java/com/flowingcode/vaadin/addons/googlemaps/CustomizedMarkerIconsDemo.java (2)

39-39: LGTM! Map center coordinates updated consistently.

The coordinates have been updated to match the same center point used across demo files, providing a consistent reference location for testing.

---

44-44: LGTM! Marker icon URL updated to latest version.

The marker icon URL has been updated from the 2020 version to the 2025 version, which aligns with the PR objective of updating FlowingCode's logo in the demo.

src/test/java/com/flowingcode/vaadin/addons/googlemaps/GoogleMapsDemo.java (3)

44-44: LGTM! Map center coordinates updated consistently.

The coordinates have been updated to provide a consistent reference location across demo files.

---

70-70: LGTM! Marker icon URL updated to latest version.

The marker icon URL has been updated from the 2020 version (FCMarker.png) to the 2025 version (marker_1.png), which successfully addresses the PR objective of updating FlowingCode's logo in the demo.

---

70-70: Verified: marker icon URL is accessible — no action required.
HTTP/2 200; content-type: image/png; content-length: 2745.

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud