Skip to content

Issue #708: Add option to hide and reorder Share panel tabs#12373

Open
Brice150 wants to merge 2 commits into
geosolutions-it:masterfrom
Brice150:feature/issue-708
Open

Issue #708: Add option to hide and reorder Share panel tabs#12373
Brice150 wants to merge 2 commits into
geosolutions-it:masterfrom
Brice150:feature/issue-708

Conversation

@Brice150
Copy link
Copy Markdown

@Brice150 Brice150 commented May 13, 2026

Description

This PR implements the feature requested in georchestra/mapstore2-georchestra#708, allowing configuration of Share panel tabs.

  • Feature

Changes

  • Added support for tabsOrder configuration to customize the order of tabs
  • Added support for hideTabs configuration to hide specific tabs
  • Tabs are dynamically filtered and sorted based on configuration

Example :

"cfg": {
"options": {
"tabsOrder": ["permalink", "direct", "embed"],
"hideTabs": ["social"]
}
}

Breaking change

  • No

@cla-bot
Copy link
Copy Markdown

cla-bot Bot commented May 13, 2026

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Brice150.
This is most likely caused by a git client misconfiguration; please make sure to:

  1. check if your git client is configured with an email to sign commits git config --list | grep email
  2. If not, set it up using git config --global user.email email@example.com
  3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

@Brice150 Brice150 changed the title Issue 708 : possibility to mask some tabs in the fonctionnality and c… Issue #708: Add option to hide and reorder Share panel tabs May 13, 2026
Copy link
Copy Markdown
Member

@tdipisa tdipisa left a comment

Choose a reason for hiding this comment

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

@Brice150 many thanks for your contribution. However, the master branch must be the first target for new contributions. Once approved and merged on master branch a backport PR will be automatically created depending on the target stable branch.
Since you recently signed the CLA you should not have problems in proceedting with raising a PR to master first. Thank you for your understanding.

@cla-bot
Copy link
Copy Markdown

cla-bot Bot commented May 13, 2026

In order to contribute to the MapStore project, the CLA (Contributor License agreement) should be sent signed to GeoSolutions. Please consult contributing rules at: https://github.com/geosolutions-it/MapStore2/wiki/Contributing-to-MapStore#contributing-code

@Brice150 Brice150 changed the base branch from 2025.02.xx to master May 13, 2026 13:43
@Brice150 Brice150 force-pushed the feature/issue-708 branch from c910164 to 4ad3658 Compare May 13, 2026 13:48
@cla-bot
Copy link
Copy Markdown

cla-bot Bot commented May 13, 2026

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Brice150.
This is most likely caused by a git client misconfiguration; please make sure to:

  1. check if your git client is configured with an email to sign commits git config --list | grep email
  2. If not, set it up using git config --global user.email email@example.com
  3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

@Brice150
Copy link
Copy Markdown
Author

@Brice150 many thanks for your contribution. However, the master branch must be the first target for new contributions. Once approved and merged on master branch a backport PR will be automatically created depending on the target stable branch. Since you recently signed the CLA you should not have problems in proceedting with raising a PR to master first. Thank you for your understanding.

I rebased and now master is the target branch

@cla-bot
Copy link
Copy Markdown

cla-bot Bot commented May 13, 2026

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Brice150.
This is most likely caused by a git client misconfiguration; please make sure to:

  1. check if your git client is configured with an email to sign commits git config --list | grep email
  2. If not, set it up using git config --global user.email email@example.com
  3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

@tdipisa
Copy link
Copy Markdown
Member

tdipisa commented May 13, 2026

@Brice150 please take into account this message for correcting your setup accordingly. Thanks

@Brice150 Brice150 force-pushed the feature/issue-708 branch from e92a210 to c00f5a5 Compare May 13, 2026 15:33
@cla-bot cla-bot Bot added the CLA Ready label May 13, 2026
@Brice150 Brice150 force-pushed the feature/issue-708 branch from c00f5a5 to 9d1e763 Compare May 13, 2026 15:35
@Brice150 Brice150 requested a review from tdipisa May 13, 2026 15:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants