gjerokrsteski on master
Create php.yml (compare)
gjerokrsteski on master
Update issue templates (compare)
gjerokrsteski on master
run ci pipeline including PHP v… (compare)
gjerokrsteski on master
use colors while running tests (compare)
gjerokrsteski on master
Create ISSUE_TEMPLATE.md (compare)
gjerokrsteski on master
move Scrutinizer Quality Score … (compare)
gjerokrsteski on master
pin a Dependency Status bdage (compare)
gjerokrsteski on master
use php as keyword for composer… (compare)
gjerokrsteski on master
change version to 1.11.0 (compare)
gjerokrsteski on v1.11.0
gjerokrsteski on master
Fix & update travis config (#31… (compare)
gjerokrsteski on master
allowed Transphporm to accept r… (compare)
Hello folks,
Garret asked me to create this chat in order to be able to create the roadmap for PIMF v2.0.0
Reason for that decision is, that we want still stay focused to keep PIMF being a micro framework, and there are features that do not have to be reinvented.
Anyway, I hope you are not scared of that :-)
From my side that's about enough for v2.0.0
If you have any other ideas for features or improvements, then please write them here ... and we will try to prioritize as good as possible.
Thanks a lot, I look forward to your feedback :-)
I am about to start working on my own full-stack framework, but as a micro framework I think PIMF has promise. If we can keep it running fast while improving the code structure, version 2 will be great.
I like the idea of using a DIC, but I can understand why you think it's not a good fit. Can you tell me what DIC packages you like? That may help me understand how it would complicate things.
# upstream is the name which you give to the remote
git remote add upstream git@github.com:gjerokrsteski/pimf-framework.git
git fetch upstream
# prefer using "git rebase upstream/master master" in order to avoid a merge commit if possible
git merge upstream/master master
git push origin master
push
)