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

Composerify #47

Open
MaximeCulea opened this issue Nov 24, 2016 · 2 comments
Open

Composerify #47

MaximeCulea opened this issue Nov 24, 2016 · 2 comments
Assignees
Milestone

Comments

@MaximeCulea
Copy link
Contributor

Improve plugin integration by adding composer.json file.

If the custom settings.api by Tareq was blocking it, now it can be included in composer's requirements.

@MaximeCulea
Copy link
Contributor Author

MaximeCulea commented Nov 27, 2016

As the zip can differ from the repo package, Tareq's Setting API could be deleted and integrated only by Composer.
This means that each release zip must contain full package for download purpose without composer dependencies. Either, people using composer could only use composer install to get the plugin and needed requirements.

/!\ Btw, as Tareq's setting API has been updated, don't forget to use the new one. /!\

So I update the todo list :

  • Add composer.json
  • Update Setting API (1.2)
  • Refactor display with new API
  • Full composer integration/handle release packages

@MaximeCulea
Copy link
Contributor Author

As API has changed, It would be preferable to refactor the way to display current sections into pages, then each notification into a section as the setting API works.

MaximeCulea added a commit that referenced this issue Dec 6, 2016
@MaximeCulea MaximeCulea modified the milestones: 1.0.3, 1.0.2 Dec 18, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant