What's in this PR?

We have some kind of a Chicken & Egg problem when try to use the Route entity with a Entity which using auto increment ids. As the Route entity requires the resourceId but the Entity itself does not yet have a getId().

In this pull request we are adding a new way to create a instance of Route without knowing the related resourceId at that time.

-       $route = new Route(
+       $route = Route::createRouteWithTempId(
            $localizedDimensionContent::getResourceKey(),
-           (string) $localizedDimensionContent->getResourceId(),
+           fn (): string => (string) $localizedDimensionContent->getResourceId(),
            $locale,
            $routeSlug,
        );

This new method will generate the route with a resourceId temp::<ulid::base58> which later will be replaced in a postFlush listener with the correct id of the entity. As discussed with @Prokyonn we decided to use ulid::base58 to avoid confusen with uuid, so if something went wrong and they see in the database temp::ulid they not confuse it with a uuid which may exist as page or article.

Why?

As the Route entity can be used also for entities which has a autoincremented ids which only exists after flush.

Example Usage

If you have a entity with autoincrement id use the createRouteWithTempId to create your route and the bundle will automatically on postFlush call your callback method to get the correct id and set it to the route entity correctly:

       $route = Route::createRouteWithTempId(
           'example',
           fn (): string => (string) $entity->getId(),
           'en',
           '/new-slug',
       );

       $entity->setRoute($route);

To Do

• Create test for this
• Create a documentation PR