Fix: #2388 Update container position of Map and Feature Editor position.

[anup39]

This PR fixes the position of the Map and the Feature Editor.

Note : There are some problem in the icon size (filter in table) which is a different issue and is originated from recent submodule update in my local.

[gemini-code-assist]

Summary of Changes

Hello @anup39, I'm Gemini Code Assist¹! 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 addresses a UI rendering issue by adjusting the container positions of the Map and Feature Editor components within the application's configuration. The changes ensure that these key elements are displayed in their intended locations, improving the overall user experience and visual layout.

Highlights

• Map Plugin Container Position: Updated the configuration for various map-related plugins to set their containerPosition to 'background', ensuring they render correctly behind other UI elements.
• Feature Editor Container Position: Modified the configuration for the FeatureEditor plugin to set its containerPosition to 'bottom', fixing its visual placement on the screen.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• geonode_mapstore_client/static/mapstore/configs/localConfig.json
  • Added "containerPosition":"background" to multiple map-related plugin configurations.
  • Added "containerPosition":"bottom" to the "FeatureEditor" plugin configurations.

Activity

• No human activity has been recorded on 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. ↩

[gemini-code-assist]

Code Review

The pull request addresses the positioning of the Map and Feature Editor containers by introducing a "containerPosition" property in localConfig.json. This change appears to correctly resolve the UI layout issues as described in the PR title and body. The modifications are consistent across multiple configurations for the 'Map' plugin, setting its container position to 'background', and for the 'FeatureEditor' plugin, setting its container position to 'bottom'. The changes are straightforward and directly target the reported UI problem.

[subashtiwari1010]

@anup39 The icon size issues is resolved in #2387 PR.