CB-5197 create main connection fields dynamically

[yagudin10]

No description provided.

[DenisSinelnikov]

may be move dataSourceContainer.getConnectionConfiguration() to parameter

[alexander-skoblikov]

mainProperties sounds strange 🤔

[alexander-skoblikov]

same here

[sergeyteleshev]

may be like this? i dont like when we trick TS like this with "!"

Suggested change

	const config = contexts.getContext(connectionConfigContext);
	const stateContext = contexts.getContext(formStateContext);
	const driver = await this.dbDriverResource.load(data.config.driverId!, ['includeProviderProperties']);
	const driver = await this.dbDriverResource.load(data.config.driverId!, ['includeProviderProperties', 'includeMainProperties']);
	if (!data.info || !data.config.driverId) {
	return;
	}
	const config = contexts.getContext(connectionConfigContext);
	const stateContext = contexts.getContext(formStateContext);
	const driver = await this.dbDriverResource.load(data.config.driverId, ['includeProviderProperties', 'includeMainProperties']);

[sergeyteleshev]

should we add here also extra check that some properties are exists like you did in DriverConfigurationType.Custom a little bit below?

[sergeyteleshev]

and here

[Wroud]

i will suggest to use switch(tempConfig.configurationType) to exclude unwanted effects from different types of configuration so you can be sure that you'll sent only state related to selected configuration

for example:
tempConfig.mainProperties = toJS(state.config.mainProperties); always set

it can reflect on:

if (tempConfig.configurationType === DriverConfigurationType.Custom && !!driver.mainProperties?.length) {
      tempConfig.mainProperties = this.prepareDynamicProperties(driver.mainProperties, tempConfig.mainProperties, tempConfig.configurationType);
    }