Auto-generated configs use table names in provider types but schema names in service collections

[PZahnen]

ldproxy editor Version

v2.0.2

Current Behavior

When creating new configurations via auto generate, the provider config writes table keys into types (e.g. types.tablename), while the generated service config uses schema names for collections (e.g. collections.vineyards). This leads to inconsistent identifiers between provider and service configs.

Expected Behavior

Service/tile generation should use the same type/table names as the provider types entries, not schema keys. Provider and service configs should reference identical collection/type identifiers.

Steps to Reproduce

Create provider and service configuration with editor.