@snteam/amplify-angular-core 1.0.37 → 1.0.39
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/index.d.ts
CHANGED
|
@@ -478,7 +478,7 @@ declare class ConfigurationAnalyzerService implements ConfigurationAnalyzer {
|
|
|
478
478
|
*/
|
|
479
479
|
generateNestedFieldSelectors(fieldName: string, targetModel: string): string[];
|
|
480
480
|
/**
|
|
481
|
-
* Enhanced field selector determination that supports nested paths
|
|
481
|
+
* Enhanced field selector determination that supports nested paths and handles different relationship types
|
|
482
482
|
*/
|
|
483
483
|
determineFieldSelectorsEnhanced(targetModel: string, fieldName?: string): string[];
|
|
484
484
|
/**
|
|
@@ -922,9 +922,14 @@ declare class AmplifyModelService {
|
|
|
922
922
|
private shouldRetryOnError;
|
|
923
923
|
/**
|
|
924
924
|
* Validate that relationship field data is populated in query results
|
|
925
|
-
* Enhanced with comprehensive error logging
|
|
925
|
+
* Enhanced with comprehensive error logging and flexible validation
|
|
926
926
|
*/
|
|
927
927
|
private validateRelationshipFieldPopulation;
|
|
928
|
+
/**
|
|
929
|
+
* Check if a record has nested relationship data based on field patterns
|
|
930
|
+
* This helps validate cases where selection sets use nested field access like "table.id", "table.name"
|
|
931
|
+
*/
|
|
932
|
+
private hasNestedRelationshipData;
|
|
928
933
|
/**
|
|
929
934
|
* Log query attempt details
|
|
930
935
|
*/
|