Consider dropping type duplicates in schema for resources #1745
Labels
impact/breaking
Fixing this issue will require a breaking change
kind/engineering
Work that is not visible to an external user
kind/enhancement
Improvements or new features
Hello!
Issue details
Currently we seem to add resources into types as well. This behavior has been supported for backward compatibility with perhaps pre-schema based implementation. We should take the opportunity to remove the unnecessary duplication at next major iteration
Affected area/feature
SDK size/surface area.
The text was updated successfully, but these errors were encountered: