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

Update modules after changes from the core, use two different templat… #1

Merged
merged 20 commits into from Jul 4, 2019

Conversation

@jolelievre
Copy link
Contributor

commented May 17, 2019

Update modules after changes from the core (class name changes, hooks removed, ...)
Use two different templates to extend modern and classic themes

"example"
],
"author": "PrestaShop SA <contact@prestashop.com>",
"license": "OSL-3.0",

This comment has been minimized.

Copy link
@PierreRambaud

PierreRambaud Jul 4, 2019

AFL for modules? 🤔

This comment has been minimized.

Copy link
@jolelievre

jolelievre Jul 4, 2019

Author Contributor

since it's an example module I thought OSL was right, not sure though

Show resolved Hide resolved package.json Outdated
@PierreRambaud
Copy link

left a comment

This is an example, no need to be too strict!

@jolelievre jolelievre merged commit 9ac1922 into master Jul 4, 2019

@PierreRambaud PierreRambaud deleted the update-module-for-release branch Jul 4, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.