ColemanDunn

Anything blocking this from getting approved?

I also came across this problem and made my own solution by dynamically creating unique constraints based on the 'deleted' field in the metaclass. Inspired by this post here: https://stackoverflow.com/questions/45687127/altering-unique-fields-of-inherited-django-model....

For the second commit: If the project structure as shown in the [DRF quickstart guide](https://www.django-rest-framework.org/tutorial/quickstart/) is followed, in which your app is 'nested' within your project, then your app_config.name will...

Slightly clearer solution [here](https://github.com/docker/getting-started/issues/231#issuecomment-1018641262) [Slightly more context](https://github.com/docker/getting-started/issues/231#issuecomment-1110175000)

could we get this merged?

> Where are you looking at warnings? sorry I missed this. what do you mean exactly? The warnings show up in my IDE if that is what you mean

> removing the `"use client"` directive from the child component will resolve this warning, That is the intended fix for this warning > although the child component still will be...

> To me, it is important that I label all client components with the 'use client' directive. > > Our editors should either be smart enough to figure out that...

> And a computer can make a graph and determine if it's being used by a server component and _only_ then show the alert - otherwise there isn't an error....

> but why isn't it experimental? Because it is working as intended except for the title of this issue > It's nice that next build doesn't fail due to these...