feat: namespace migration for settings - #396
Draft
joerivanveen wants to merge 1 commit into
Draft
Conversation
❌ 1 Tests Failed:
View the top 1 failed test(s) by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
joerivanveen
force-pushed
the
feat/namespace-migration-for-settings
branch
from
October 2, 2025 13:15
0cde2f5 to
f85f36f
Compare
joerivanveen
force-pushed
the
feat/namespace-migration-for-settings
branch
from
October 2, 2025 13:31
f85f36f to
19a9bf4
Compare
FreekVR
force-pushed
the
main
branch
2 times, most recently
from
February 17, 2026 09:09
ec8abf1 to
e2ffc92
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This namespace migration was created during the rework to get the proposition from the api key. It was decided not to rename the module because that would require an uninsstall + reinstall into PrestaShop, which enforces the name of the module to be the same as the folder and the initial class php file.
Here it is stored for use with a later major release that will rename the module to align more with the names in other plugins.