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

Create separate config for cleaning up fresh Laravel installation #65

Closed
krzysztofrewak opened this issue Apr 25, 2022 · 0 comments · Fixed by #86
Closed

Create separate config for cleaning up fresh Laravel installation #65

krzysztofrewak opened this issue Apr 25, 2022 · 0 comments · Fixed by #86
Labels
enhancement New feature or request

Comments

@krzysztofrewak
Copy link
Member

A fresh Laravel installation has a lot of useless stuff like stupid comments, no return types, useless methods and so on. It would be nice if we could create a separate config with prefabricated set of rules to clean this up.

This could be used in normal codestyle.php file like that:

<?php

declare(strict_types=1);

use Blumilk\Codestyle\FreshLaravelConfig;
use Blumilk\Codestyle\Configuration\Defaults\Paths;

$config = new FreshLaravelConfig();
return $config->config();

or maybe:

<?php

declare(strict_types=1);

use Blumilk\Codestyle\Config;
use Blumilk\Codestyle\Configuration\Defaults\Paths;

$config = new Config();
return $config->freshLaravelConfig();

Or maybe even as a script in ./vendor/bin/codestyle --laravel.

@krzysztofrewak krzysztofrewak added the enhancement New feature or request label Apr 25, 2022
krzysztofrewak added a commit that referenced this issue Dec 7, 2022
krzysztofrewak added a commit that referenced this issue May 30, 2023
# Conflicts:
#	src/Configuration/Defaults/CommonRules.php
#	tests/codestyle/CodestyleTest.php
krzysztofrewak added a commit that referenced this issue May 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant