Rostislav Simonik

@valajczech can you please create a minimalistic repo that replicates your case? That would give us more context to provide you support.

But `[email protected]` is only for `[email protected]`, so you would need to go back to `[email protected]`, I don't recall which `[email protected]` is needed for `4.13.0` if, for some reason, you would...

but your issue can originate from a different root cause, that's why better to provide a replicable repo if those versions won't help.

@RomanTsegelskyi that would be great, feel free to start.

@sargentieri hello, just want to check if you want to contribute in general or to CRUD schema?

@sargentieri I have created a discord server so we can discuss more operatively, feel free to reach out to me there

@gre Thanks, but it's different use case. We want throw warning when another developer is trying to use type which is deprecated. In your case it's about marking deprecated attributes,...

@gre Yes, both use cases are life capable and can be covered. I have just written to differentiate cases.

@langpavel two issues, two use cases, two implementations are 3 different things. I'm happy with any configuration if use case presented by us, will be covered. ;)