Skip to content
This repository has been archived by the owner on May 5, 2023. It is now read-only.

What do we do with Composer? #15

Open
viktorix opened this issue Jan 13, 2023 · 5 comments
Open

What do we do with Composer? #15

viktorix opened this issue Jan 13, 2023 · 5 comments
Labels
question Further information is requested

Comments

@viktorix
Copy link
Member

Composer was added in PR #169. Do we keep it or get rid of it?

@viktorix viktorix added the question Further information is requested label Jan 13, 2023
@mattyrob
Copy link
Collaborator

I'd suggest we keep, we are now using Composer to make available the necessary dependences for development - things like phpcs and the Coding Standards libraries as well as PHPUnit Polyfills that are used in the automates testing.

@viktorix
Copy link
Member Author

@mattyrob so that means we need access to https://packagist.org/packages/classicpress/classicpress? Right now we don't have it.

@viktorix
Copy link
Member Author

Also, there's an old issue about Composer autoloading. We should see if this is something we need or close it:
ClassicPress/ClassicPress#247

@mattyrob
Copy link
Collaborator

@viktorix - The packagist site does seem to be updating when we make a new release, I presume they scan us for updates automatically, but agreed, we need to transfer ownership to the project.

@viktorix
Copy link
Member Author

I think I'm getting access to the packagist package. Working with packagist support on this.

viktorix pushed a commit that referenced this issue Feb 1, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
question Further information is requested
Projects
No open projects
Status: Issues: Discussion
Development

No branches or pull requests

2 participants