home.social

#rectorextension — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #rectorextension, aggregated by home.social.

  1. RE: infosec.exchange/@art4/1157471

    Just in time for the end of 2025 (at least in my time zone), I released version 1.0.0 of my new #RectorExtension that replaces the native type declaration set. The special thing about it: no breaking changes!

    This means: no changes to parameter types or return types if your class/method is not private or final. This is particularly important for library maintainers who want to use #Rector but don't want to have any breaking changes.

    If you are a maintainer of a #PHP library and #backwardcompatibility is important to you, then check it out on #packagist:

    packagist.org/packages/art4/re

    Happy new year! 🥳

  2. RE: infosec.exchange/@art4/1157471

    Just in time for the end of 2025 (at least in my time zone), I released version 1.0.0 of my new #RectorExtension that replaces the native type declaration set. The special thing about it: no breaking changes!

    This means: no changes to parameter types or return types if your class/method is not private or final. This is particularly important for library maintainers who want to use #Rector but don't want to have any breaking changes.

    If you are a maintainer of a #PHP library and #backwardcompatibility is important to you, then check it out on #packagist:

    packagist.org/packages/art4/re

    Happy new year! 🥳

  3. RE: infosec.exchange/@art4/1157471

    Just in time for the end of 2025 (at least in my time zone), I released version 1.0.0 of my new #RectorExtension that replaces the native type declaration set. The special thing about it: no breaking changes!

    This means: no changes to parameter types or return types if your class/method is not private or final. This is particularly important for library maintainers who want to use #Rector but don't want to have any breaking changes.

    If you are a maintainer of a #PHP library and #backwardcompatibility is important to you, then check it out on #packagist:

    packagist.org/packages/art4/re

    Happy new year! 🥳

  4. RE: infosec.exchange/@art4/1157471

    Just in time for the end of 2025 (at least in my time zone), I released version 1.0.0 of my new #RectorExtension that replaces the native type declaration set. The special thing about it: no breaking changes!

    This means: no changes to parameter types or return types if your class/method is not private or final. This is particularly important for library maintainers who want to use #Rector but don't want to have any breaking changes.

    If you are a maintainer of a #PHP library and #backwardcompatibility is important to you, then check it out on #packagist:

    packagist.org/packages/art4/re

    Happy new year! 🥳

  5. RE: infosec.exchange/@art4/1157471

    Just in time for the end of 2025 (at least in my time zone), I released version 1.0.0 of my new #RectorExtension that replaces the native type declaration set. The special thing about it: no breaking changes!

    This means: no changes to parameter types or return types if your class/method is not private or final. This is particularly important for library maintainers who want to use #Rector but don't want to have any breaking changes.

    If you are a maintainer of a #PHP library and #backwardcompatibility is important to you, then check it out on #packagist:

    packagist.org/packages/art4/re

    Happy new year! 🥳

  6. I'm currently working on a #RectorExtension that replaces the native type declaration set. The special thing about it: no breaking changes!

    This means: no changes to parameter types or return types if your class/method is not private or final. This is particularly important for library maintainers who want to use #Rector but don't want to have any breaking changes.

    If you are a maintainer of a #PHP library and #backwardcompatibility is important to you, then check it out on #packagist: packagist.org/packages/art4/re

    And feel free to give me feedback.

  7. I'm currently working on a #RectorExtension that replaces the native type declaration set. The special thing about it: no breaking changes!

    This means: no changes to parameter types or return types if your class/method is not private or final. This is particularly important for library maintainers who want to use #Rector but don't want to have any breaking changes.

    If you are a maintainer of a #PHP library and #backwardcompatibility is important to you, then check it out on #packagist: packagist.org/packages/art4/re

    And feel free to give me feedback.

  8. I'm currently working on a #RectorExtension that replaces the native type declaration set. The special thing about it: no breaking changes!

    This means: no changes to parameter types or return types if your class/method is not private or final. This is particularly important for library maintainers who want to use #Rector but don't want to have any breaking changes.

    If you are a maintainer of a #PHP library and #backwardcompatibility is important to you, then check it out on #packagist: packagist.org/packages/art4/re

    And feel free to give me feedback.

  9. I'm currently working on a #RectorExtension that replaces the native type declaration set. The special thing about it: no breaking changes!

    This means: no changes to parameter types or return types if your class/method is not private or final. This is particularly important for library maintainers who want to use #Rector but don't want to have any breaking changes.

    If you are a maintainer of a #PHP library and #backwardcompatibility is important to you, then check it out on #packagist: packagist.org/packages/art4/re

    And feel free to give me feedback.

  10. I'm currently working on a #RectorExtension that replaces the native type declaration set. The special thing about it: no breaking changes!

    This means: no changes to parameter types or return types if your class/method is not private or final. This is particularly important for library maintainers who want to use #Rector but don't want to have any breaking changes.

    If you are a maintainer of a #PHP library and #backwardcompatibility is important to you, then check it out on #packagist: packagist.org/packages/art4/re

    And feel free to give me feedback.