ekmungai / eloquent-ifrs

Eloquent Double Entry Accounting with a focus on IFRS Compliant Reporting
MIT License
334 stars 68 forks source link

Upgrade: Bump nunomaduro/larastan from 0.7.12 to 1.x-dev #110

Closed dependabot[bot] closed 2 years ago

dependabot[bot] commented 2 years ago

Bumps nunomaduro/larastan from 0.7.12 to 1.x-dev.

Release notes

Sourced from nunomaduro/larastan's releases.

0.7.15

What changed?

Fixed

  • Removed tags from conditional rules.

Full Changelog: https://github.com/nunomaduro/larastan/compare/v0.7.14...v0.7.15

0.7.14

What's Changed

Fixed

  • Fixed template resolution when flatMap's callback returns an Enumerable (#970) Thanks @​bastien-phi

Added

  • Detection of fields added/modified a migration $table->after() method (Added in Laravel 8.27). (#972) Thanks @​jimohalloran
  • Add new rule NoModelMake to prevent inefficient model instantiation (#976) Thanks @​spawnia

New Contributors

Full Changelog: https://github.com/nunomaduro/larastan/compare/v0.7.13...v0.7.14

0.7.13

Fixed

Added

  • Support global macros on the eloquent query builder.
  • Partial support for defining columns with foreignIdFor in migrations. (#932) Thanks @​Josh-G
  • Extension for collect helper and Collection::make (#904)
  • Support for scopes defined in model docblocks (88422fb)
  • rescue helper stub (#961) Thanks @​jrmajor
  • Added trait_exists to ensure orchestra/testbench is installed for packages. (#957) Thanks @​rajyan
  • Larastan now finds Laravel app even if it's not in the current working directory
Changelog

Sourced from nunomaduro/larastan's changelog.

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog and this project adheres to Semantic Versioning.

[Unreleased]

[2.0.0] - 2022-01-26

Changed

  • Dropped support for Laravel versions older than 9.
  • Moved all Collection stubs to Laravel core.

Added

[1.0.3] - 2022-01-20

[1.0.2] - 2021-11-23

Added

Fixed

Changed

[1.0.1] - 2021-11-06

Changed

  • Fix groupBy Collection method signature
  • Renamed CheckJobDispatchArgumentTypesCompatibleWithClassConstructorRule to CheckDispatchArgumentTypesCompatibleWithClassConstructorRule by @​canvural in nunomaduro/larastan#1003
  • CheckDispatchArgumentTypesCompatibleWithClassConstructorRule now checks for argument types compatibility with the class constructor for both Event and Job classes. by @​canvural in nunomaduro/larastan#1003

... (truncated)

Upgrade guide

Sourced from nunomaduro/larastan's upgrade guide.

Upgrade Guide

Upgrading to 2.0.0 from 1.x

Eloquent Collection now requires 2 generic types

In Larastan 1.x, Eloquent Collection was defined with only one generic type. Just the model type. But starting with Laravel 9, all collection stubs are now moved into the Laravel core. And as part of that migration process, the collection type is now defined with 2 generic types. First is collection item key, second is collection item value. So if you had a docblock like this Collection<User> now you should change it to Collection<int, User>.

Removed configuration checkGenericClassInNonGenericObjectType: false from default config

In Larastan 1.x, we set the checkGenericClassInNonGenericObjectType to false by default. In 2.0.0, this is removed from the config. If you want to keep the same behavior, you can set it to false in your config.

Upgrading to 0.7.11

Laravel 8 Model Factory support

0.7.11 adds support for Laravel 8 model factory return types and methods. But there is one step you need to do before taking advantage of this.

Because Factory class is marked as generic now, you need to also specify this in your model factories.

So for example if you have UserFactory class, the following change needs to be made:

<?php

/** @​extends Factory<User> */ class UserFactory extends Factory { // ... }

So general rule is that @extends Factory<MODELNAME> PHPDoc needs to be added to factory class, where MODELNAME is the model class name which this factory is using.

Upgrading to 0.7.0

databaseMigrationsPath parameter is now an array

databaseMigrationsPath parameter is changed to be an array from string. To allow multiple migration paths.

Upgrading to 0.6

In previous versions of Larastan, reportUnmatchedIgnoredErrors config value was set to false by Larastan. Larastan no longer ignores errors on your behalf. Here is how you can fix them yourself:

Result of function abort (void) is used

Stop return-ing abort.

-return abort(401);
+abort(401);
</tr></table> 

... (truncated)

Commits


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot] commented 2 years ago

Looks like nunomaduro/larastan is no longer updatable, so this is no longer needed.