Releases

[mitchellvanw]

Hello Everybody, I decided to create this issue to inform all of you on the updates that are coming. Soon I'm releasing version 0.6. This version will include:

• several bug fixes
• all Doctrine CLI commands in Artisan
• lazy loading Doctrine in Artisan (So it's not loaded on every artisan command you do)

According to Taylor's tweet he'll be releasing Laravel 5 next week. When the new major version of Laravel is released version 1.0 of this package will be released and support for Laravel 4 for the Laravel Doctrine package will be moved under the branch laravel4. From this point on only bugfixes for Laravel 4 will be supported.

And now the exciting part..

A lot of people have been requesting the ability to extend the Doctrine Configuration, but for us to support all of the Configuration options is not feasible. So we've come up with a solution that will give you the flexibility you need. Shortly after version 1.0 we're going to release extensions. In your applications you'll be able to create extension classes and have access to Configuration, Entity Manager, the package config, Event Manager, and Annotation Reader.

We're still looking at finalizing this, but an extension will look something like this:

class SoftDeleteableExtension implements Extension {

    public static function loadExtension(Configuration $metadata, ExtendedMappingDriverChain $driverChain, CachedReader $cachedAnnotationReader, EntityManager $entityManager, EventManager $eventManager,  $config) {
        $metadata->addFilter('trashed', TrashedFilter::class);
        $eventManager->addEventListener(Events::onFlush, new SoftDeleteableListener);
        $entityManager->getFilters()->enable('trashed');
    }
}

Even the Laravel Doctrine package configurations will be extensions. This will make it possible for you to disable the package's extensions and replace them with your own. Because this will break BC it'll be released under version 2.0.

I'll be tweeting about new versions and updates at @mitchellvanw.

Thanks!

[nWidart]

Good news :)

Will the Doctrine Extensions work with this new structure ?

[mitchellvanw]

@nWidart No, I've looked at those and decided not to use them, it'll be similar though. It would be far easier to create our own system and not worry about the them. What soon is possible is for others to create extensions and put them on Packagist

[nWidart]

Oh that's too bad! Those extensions have -very- helpful helpers, like for instance the Translatable, Translator, Tree, Sluggable, Loggable, Sortable, etc. etc. . Why re-invent the wheel if it already exists?

[mitchellvanw]

Some look great and we might make them as well, in our own way. I personally don't like some of the decisions made in that package. I also believe that reinventing the wheel could be a good thing. Even if it's just to look at a problem from a different angle

[soyuka]

As long as we can add our own Listeners this seems great!

Will it be possible to unload a specific extension? Assuming I don't want to use SoftDelete but I want to keep the PrefixTable out of the box?

Thanks for the great work!

[mitchellvanw]

Yes, @soyuka. You'll have complete control. The Proxy configuration will be an extension as well. What this package will become is a bootstrap for Doctrine with some basic extensions, if you need some logic in whatever happens with the proxy config then you just create your own proxy extension and use that instead of the default one.

[soyuka]

👍

So, as Doctrine Extensions are basically Listeners, they could be implemented by Laravel-Doctrine users.

Proxying commands from artisan through Doctrine directly will be very useful too! Excited about this :).

You'll still keep the TablePrefix and Softdelete extensions in this repo?

[mitchellvanw]

Yes, these extensions will remain in this package. Any other extension we add in the future we'll be added to the core under proposal otherwise we'll create a separate package

[fedeisas]

@mitchellvanw I'm currently migrating a PHP project from another framework into Laravel. It uses Doctrine repositories extensively. I'd love to see something about EntityRepository as discussed on #50.

[FoxxMD]

Laravel 5 has been out for over a month now -- when is 1.0 coming? There's a huge amount of pull requests for L5 support that could be very useful...

[sebastiaanluca]

Any updates? Is this project still actively being maintained?

[nWidart]

Doubtful, I use this forked version on laravel 5.

[ldebrouwer]

Could the project perhaps be handed over to the community to ensure further development?

[kirkbushell]

I believe the community needs something a step further. Laravel-doctrine is a great project, something @mitchellvanw and i have been working on for a while, but alas real life has gotten in the way of maintaining this project the last 3 or 4 months.

I'm working on another project that basically makes doctrine the default implementation for Laravel, rather than Eloquent, which results in a much slimmer, nicer build of Laravel.

[boris-glumpler]

@kirkbushell Sounds interesting. Got a link maybe to check it out?

[ldebrouwer]

@kirkbushell Sounds very interesting indeed. If you need additional hands, please let me know.

[kirkbushell]

Not yet, as I'm still planning the project out. At it's core, however - will have the laravel-doctrine package, along with laravel.

[FoxxMD]

For anyone viewing this issue please use laravel-doctrine/orm instead!

We have a much more feature-complete, stable, and up to date integration for Doctrine 2 with Laravel 5+

[mitchellvanw]

Closing because project is no longer maintained. Thanks.