<p>I&#39;m using slug-based routing, like this</p>
<pre><code>myapp.com/posts/first-post
</code></pre><p>I have a Post entity, and a PostTranslation entity, When I create a Post entity, 2 PostTranslation entities are being created (for each language), and they have an empty slug and title field, so the user can choose this. The issue is that when I want to browse to this post, and the user didn&#39;t set a slug yet, it will break. How would you handle this?</p>


I'm using slug-based routing, like this

```
myapp.com/posts/first-post
``` 
    
I have a Post entity, and a PostTranslation entity, When I create a Post entity, 2 PostTranslation entities are being created (for each language), and they have an empty slug and title field, so the user can choose this. The issue is that when I want to browse to this post, and the user didn't set a slug yet, it will break. How would you handle this?




How do you handle slug-based routing, but translatable entities that have an empty slug at first? Which breaks..

Product

Explore

Company

Blogs

Support