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

#8586 Make eager option configurable for extensions shared libraries #8587

Conversation

alexander-fedorenko
Copy link
Contributor

Description

With the changes suggested in PR each extension will have a way to configure eager option for shared libraries.

Please check if the PR fulfills these requirements

What kind of change does this PR introduce? (check one with "x", remove the others)

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Other... Please describe:

Issue

What is the current behavior?
#8586

What is the new behavior?
Eager option can be overridden by configuration passed from extension

Breaking change

Does this PR introduce a breaking change? (check one with "x", remove the other)

  • Yes, and I documented them in migration notes
  • No

Other useful information

@tdipisa tdipisa added the BackportNeeded Commits provided for an issue need to be backported to the milestone's stable branch label Sep 14, 2022
@tdipisa tdipisa merged commit 3c31f3c into geosolutions-it:master Sep 14, 2022
@tdipisa
Copy link
Member

tdipisa commented Sep 14, 2022

@alexander-fedorenko @ElenaGallo this is scheduled for 2022.02.01 so please let's wait the delivery of 2022.02.00 before backporting this. you can start testing on DEV anyway @ElenaGallo.

@allyoucanmap
Copy link
Contributor

@tdipisa @ElenaGallo This is not possible to test via UI, this fix will allows to set a flag to improve the final bundle for the extensions. We need to build an extension using this fix to verify the improvement.

@tdipisa
Copy link
Member

tdipisa commented Sep 14, 2022

@allyoucanmap

We need to build an extension using this fix to verify the improvement.

so that's the test no? :-)

@tdipisa
Copy link
Member

tdipisa commented Sep 29, 2022

@alexander-fedorenko can you please backport this to 2022.02.xx?

@tdipisa tdipisa added this to the 2022.02.01 milestone Sep 29, 2022
alex-fko pushed a commit to alex-fko/MapStore2 that referenced this pull request Sep 29, 2022
@tdipisa tdipisa removed the BackportNeeded Commits provided for an issue need to be backported to the milestone's stable branch label Sep 29, 2022
tdipisa pushed a commit that referenced this pull request Sep 29, 2022
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