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

[NFR]: Move Collection under Support #15700

Closed
niden opened this issue Oct 1, 2021 · 1 comment · Fixed by #15701
Closed

[NFR]: Move Collection under Support #15700

niden opened this issue Oct 1, 2021 · 1 comment · Fixed by #15701
Labels
5.0 The issues we want to solve in the 5.0 release breaks bc Functionality that breaks Backwards Compatibility enhancement Enhancement to the framework

Comments

@niden
Copy link
Member

niden commented Oct 1, 2021

Phalcon\Collection\Collection is a support class for the framework. It needs to be moved/renamed to Phalcon\Support\Collection.

@niden niden added the new feature request Planned Feature or New Feature Request label Oct 1, 2021
@niden niden changed the title [NFR]: Move Collection under `Support [NFR]: Move Collection under Support Oct 1, 2021
@niden niden added 5.0 The issues we want to solve in the 5.0 release breaks bc Functionality that breaks Backwards Compatibility enhancement Enhancement to the framework and removed new feature request Planned Feature or New Feature Request labels Oct 1, 2021
@niden niden linked a pull request Oct 1, 2021 that will close this issue
5 tasks
@niden
Copy link
Member Author

niden commented Oct 1, 2021

Addressed in #15701

@niden niden closed this as completed Oct 1, 2021
@niden niden moved this to Released in Phalcon v5 Aug 25, 2022
@niden niden added this to Phalcon v5 Aug 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
5.0 The issues we want to solve in the 5.0 release breaks bc Functionality that breaks Backwards Compatibility enhancement Enhancement to the framework
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant