Skip to content

fix(spp_registrant_gis): add GIS view for res.partner and promote to Beta#86

Open
emjay0921 wants to merge 1 commit into19.0from
fix/registrant-gis-view-beta
Open

fix(spp_registrant_gis): add GIS view for res.partner and promote to Beta#86
emjay0921 wants to merge 1 commit into19.0from
fix/registrant-gis-view-beta

Conversation

@emjay0921
Copy link
Contributor

Why is this change needed?

  • Opening Individual or Group forms raised "No GIS view defined for the model res.partner" because the geo_point widget calls get_edit_info_for_gis_column() which requires a GIS view to exist
  • Module was missing an app icon
  • Module is stable enough for Beta status

How was the change implemented?

  • Added GIS view (type="gis") for res.partner with id, name, display_name, coordinates fields
  • Added vector data layer linking the coordinates GeoPointField to the GIS view
  • Added OSM raster base layer (required by the edit widget for map rendering)
  • Copied app icon from spp_registry
  • Updated development_status from Alpha to Beta

New unit tests

No new tests added. Existing 5 tests in spp_registrant_gis cover field creation and coordinate assignment.

Unit tests executed by the author

Existing test suite verified.

How to test manually

  1. Upgrade spp_registrant_gis module
  2. Open any Individual or Group record — form should load without "No GIS view defined" error
  3. The GPS Coordinates map widget should render correctly in the Profile tab

Related links

…Beta

Add missing GIS view, data layer, and raster layer for res.partner
to fix "No GIS view defined" error when opening Individual/Group forms
with the geo_point widget. Also add module icon and promote to Beta.
@codecov
Copy link

codecov bot commented Mar 10, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 69.16%. Comparing base (a4f3701) to head (c924acc).

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##             19.0      #86   +/-   ##
=======================================
  Coverage   69.15%   69.16%           
=======================================
  Files         628      632    +4     
  Lines       35632    35639    +7     
=======================================
+ Hits        24643    24649    +6     
- Misses      10989    10990    +1     
Flag Coverage Δ
spp_base_common 90.26% <ø> (ø)
spp_dci_demo 69.23% <ø> (ø)
spp_mis_demo_v2 69.82% <ø> (ø)
spp_programs 45.51% <ø> (ø)
spp_registrant_gis 85.71% <ø> (?)
spp_security 66.66% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines Coverage Δ
spp_registrant_gis/__manifest__.py 0.00% <ø> (ø)

... and 3 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@gemini-code-assist
Copy link

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances the geographical information system capabilities for registrant records by introducing a dedicated GIS view for the res.partner model. This change resolves an error encountered when opening individual or group forms that require a GIS view, and it also updates the module's development status to Beta, indicating a more stable and feature-complete state. The updates ensure proper rendering of GPS coordinate map widgets and improve the overall user experience with spatial data.

Highlights

  • GIS View for Registrants: A dedicated GIS view has been added for the res.partner model, allowing for geographical representation and interaction with registrant data. This view includes essential fields like ID, name, display name, and coordinates.
  • Module Maturity Promotion: The spp_registrant_gis module has been promoted from 'Alpha' to 'Beta' development status, reflecting increased stability and readiness for broader use. Corresponding badges and warnings in documentation have been updated.
  • GIS Layer Configuration: A vector data layer has been configured to link the coordinates GeoPointField to the new GIS view, and an OpenStreetMap (OSM) raster base layer has been added to support map rendering within the GIS view.
Changelog
  • spp_registrant_gis/README.rst
    • Updated the maturity badge from Alpha to Beta.
    • Removed the 'IMPORTANT' warning regarding alpha status.
  • spp_registrant_gis/manifest.py
    • Changed the development_status from 'Alpha' to 'Beta'.
  • spp_registrant_gis/static/description/index.html
    • Updated the maturity badge image and alt text from Alpha to Beta in the HTML description.
    • Removed the 'Important' admonition about alpha version status.
  • spp_registrant_gis/views/res_partner_views.xml
    • Added a new ir.ui.view record for res.partner with type="gis".
    • Included id, name, display_name, and coordinates fields in the GIS view.
    • Created a spp.gis.data.layer record to define the vector layer for registrant coordinates.
    • Added a spp.gis.raster.layer record to include an OpenStreetMap base layer for the GIS view.
Activity
  • No specific review comments or activities have been recorded for this pull request yet.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request adds a GIS view for res.partner to resolve an error and promotes the module to Beta status. A security review found no vulnerabilities. I've also provided a suggestion to improve the name of the new raster layer for better maintainability.


<record id="gis_raster_layer_registrant_osm" model="spp.gis.raster.layer">
<field name="raster_type">osm</field>
<field name="name">Default</field>

Choose a reason for hiding this comment

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

medium

The name "Default" for the raster layer is a bit generic. Using a more descriptive name like "OpenStreetMap" would improve clarity and maintainability, making it immediately clear what this layer represents without needing to check the raster_type.

Suggested change
<field name="name">Default</field>
<field name="name">OpenStreetMap</field>

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