-
Notifications
You must be signed in to change notification settings - Fork 30
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
add support for Rector annotation-to-attribute-migration #72
Comments
IMHO the Can you share and update the Rector script accordingly? |
No, the rector script is standardised, and just converts what is already used in the annotation. Since the annotation allows I recommend we deprecate the route param, and remove it in a future v. 2 instead EDIT: Using the |
This is the recor script: return static function (ContainerConfigurator $containerConfigurator): void {
// get parameters
$parameters = $containerConfigurator->parameters();
$parameters->set(Option::PATHS, [__DIR__ . '/src']);
$parameters->set(Option::SYMFONY_CONTAINER_XML_PATH_PARAMETER, __DIR__ . '/var/cache/dev/App_KernelDevDebugContainer.xml');
$parameters->set(Option::AUTO_IMPORT_NAMES, true);
$parameters->set(Option::IMPORT_SHORT_CLASSES, false);
$services = $containerConfigurator->services();
$services->set(AnnotationToAttributeRector::class)->call('configure', [
[
AnnotationToAttributeRector::ANNOTATION_TO_ATTRIBUTE => ValueObjectInliner::inline([
new AnnotationToAttribute(\APY\BreadcrumbTrailBundle\Annotation\Breadcrumb::class),
]),
],
]);
}; Basically just tels the rector script |
Is there a way to hook into the configuration and alter the data before the attribute gets constructed? For clarity, as your comment refers to a Rector upgrade script which is not part of this bundle (yet), this issue is not an issue with this bundle's code. |
Not that i have found... I think doctrine have made their own script (pr into rector), but without that, and if we want to use rector, we need the route parameter... |
Also, the rector script is not ment to be included in the bundle, its just a one-og script designed to tell rector how to transforme the code, and then to be deleted again (it might be relevant for documentation tho to explain how to simply use attributes). |
Not including it with the bundle is ok with me, feel free to close this issue in that case. Thanks |
Yes, the problem is that the tool will fail if the attributes desnt have the argument $route. And its a very handy tool 😁 |
Hi
the parameter
$route
dissapeared in 6f4a45372d1c684cd5b4cea545712e6563f04e7d line 70.This breaks automatic transform @annotation to #[Attribute] with Rector for users that use that parameter
The text was updated successfully, but these errors were encountered: