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

Add new hooks in sql upgrade statement #1168

Open
wants to merge 1 commit into
base: dev
Choose a base branch
from

Conversation

tleon
Copy link
Contributor

@tleon tleon commented Feb 11, 2025

Questions Answers
Description? Added the new hooks from 9.0.x to the sql upgrade statement
Type? improvement
BC breaks? no
Deprecations? no
Fixed ticket? Fixes #37163
Sponsor company PrestaShop SA
How to test? CI green

@tleon tleon self-assigned this Feb 11, 2025
Copy link
Contributor

@kpodemski kpodemski left a comment

Choose a reason for hiding this comment

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

@tleon I think you should update the part that @jolelievre added in his previous PR, because, for example, the part deleting the hooks is identical

@tleon tleon force-pushed the add-new-hooks-in-sql-statement branch from c700bd9 to 3a0027e Compare February 11, 2025 17:24
Copy link

@tleon tleon requested a review from kpodemski February 11, 2025 17:25
@M0rgan01 M0rgan01 added this to the 7.0.0 milestone Feb 12, 2025
(NULL, 'dashboardData', '', '', '1'),
(NULL, 'actionPasswordRenew', '', '', '1'),
(NULL, 'actionDownloadAttachment', '', '', '1'),
(NULL, 'fooHook', '', '', '1'),
Copy link
Contributor

Choose a reason for hiding this comment

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

Is there really a hook with this name in production?

Copy link
Contributor

Choose a reason for hiding this comment

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

Copy link
Contributor

Choose a reason for hiding this comment

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

yes, this is the same problem as with the generated docs, some of the hooks should be excluded, I added more comments on this PR

Copy link
Contributor Author

Choose a reason for hiding this comment

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

In the end i don't know anymore if this command is a good idea i'm a but tired of all of this :/

Copy link
Contributor

Choose a reason for hiding this comment

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

@tleon I understand you

Copy link
Contributor

Choose a reason for hiding this comment

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

@tleon

it is a good idea and it works great, the most important remaining thing is to have block-list of hooks available, so you don't generate them, hooks from tests directory, and hooks that are deprecated :)

@M0rgan01
Copy link
Contributor

How will users be able to use hooks without them having a description ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Ready for review
Development

Successfully merging this pull request may close these issues.

3 participants