Torch
composer-patches
Our great sponsors
Torch | composer-patches | |
---|---|---|
7 | 10 | |
1,811 | 1,475 | |
- | - | |
0.0 | 7.6 | |
3 months ago | 5 days ago | |
PHP | PHP | |
MIT License | BSD 3-clause "New" or "Revised" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Torch
-
Laravel considered harmful
Torch is the proof that it's tightly coupled. Why do you even need a repo to show how to do it? Symfony doesn't have this issue. Just look at how much crap you need to wire to use a simple validation component: https://github.com/mattstauffer/Torch/blob/master/components/validation/index.php, it's garbage.
-
someone know a great php framework?
Other than the big frameworks, you could look at using Slim and other libraries/Symfony components to build your own framework - you could even use some Laravel components too.
-
Am I crazy? Do really all "PHP" companies use either Symfony or Laravel?
You can check out https://github.com/mattstauffer/Torch to see them in action
-
PHP MVC Framework
This is was game changer for me: https://github.com/mattstauffer/Torch
-
IMHO: JSX > PHP Templating
Interesting! I actually found an example here: https://github.com/mattstauffer/Torch/tree/master/components/view
composer-patches
-
Mechanics of (and ethics of) upgrading a PHP Joomla plugin
if you're using composer with joomla, and the plugin is installed via composer, you can commission someone to make the necessary changes, create a git diff patch that encapsulates the changes, then leverage cweagans/composer-patches to make it work. if/when new changes are necessary, they can build a new patch.
-
Laravel considered harmful
I've had problems with libraries using final having an API that isn't customizable enough in a particular way I need because I'm innovating in some way they could never have considered in the past, so my choice ends up either needing to fork the library or monkey patch it with https://github.com/cweagans/composer-patches so I can get rid of final so I can keep using it. They wouldn't accept a change in API or behaviour because it would break things for other users, etc.
-
Thoughts on running patches in production?
There are cool tools to integrate patches from drupal.org (or your own custom patches) into your composer managed drupal website. For example (not drupal specific but works well with drupal+composer): https://github.com/cweagans/composer-patches
-
Is there a way to apply a patch to an AUR package on the fly, without editing the PKGBUILD?
If the PR get's merged, I want `yay` or `pacman` to skip the patch. Ideally it would be declared in a pacman.patches file or similar to what https://github.com/cweagans/composer-patches provides for composer PHP package managment.
-
PSA for macOS users with composer workflows.
This has been an issue for a while, and is outlined here: - https://github.com/cweagans/composer-patches/issues/172#issuecomment-587147692 - https://github.com/cweagans/composer-patches/issues/326
-
Installing patches in Drupal 8
Install a package that allows the composer to work with patches:
- Procedure for critical dependency lagging behind?
-
Best way to handle a bug in a composer package?
And if for some reason you do not want to make a fork, you can also create a composer patch with the help of https://github.com/cweagans/composer-patches
-
Modifying a Package Controller
https://github.com/cweagans/composer-patches - this lets you patch packages when they are pulled in by Composer. I have used it in the past to get minor bugfixes into a project ASAP without having to wait for upstream or forking the entire package.
- troubles with dd or What are best practices for patching Symphony?
What are some alternatives?
pre-phpx
Repman - Repman - PHP Repository Manager: packagist proxy and host for private packages
Eloquent - [READ ONLY] Subtree split of the Illuminate Database component (see laravel/framework)
Packagist - Package Repository Website - try https://packagist.com if you need your own -
Laravel - The Laravel Framework.
comments - Native comments for your Laravel application.
BladeOne - The standalone version Blade Template Engine without Laravel in a single php file and without dependencies
ComposerRequireChecker - A CLI tool to check whether a specific composer package uses imported symbols that aren't part of its direct composer dependencies
Slim - Slim Framework 4 Skeleton Application
WordPress Packagist - WordPress Packagist — manage your plugins with Composer
blade - 🔪 A standalone version of Laravel's Blade templating engine for use outside of Laravel.
composer-diff - Compares composer.lock changes and generates Markdown report so you can use it in PR description.