Skip to content

Commit 2b277ed

Browse files
Update src/fragments/lib/troubleshooting/common/upgrading.mdx
Co-authored-by: Caleb Pollman <[email protected]>
1 parent 08855c1 commit 2b277ed

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/fragments/lib/troubleshooting/common/upgrading.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -177,7 +177,7 @@ Wherever you called `Amplify.configure({ aws-exports });` previously (usually in
177177
</Columns>
178178

179179
<Callout>
180-
`Amplify.configure()` accepts either the config JSON file or a ResourceConfig configuration object. You can use the `parseAmplifyConfig` util to parse the contents of the config JSON file **amplifyconfiguration.json** into the ResourceConfig configuration object and override properties as needed. Keep in mind that any call to configuration will fully override previous configurations, so pay special attention to nested configurations.
180+
`Amplify.configure()` accepts either the config JSON file or a `ResourcesConfig` configuration object. You can use the `parseAmplifyConfig` util to parse the contents of the config JSON file **amplifyconfiguration.json** into the `ResourcesConfig` configuration object and override properties as needed. Keep in mind that any call to configuration will fully override previous configurations, so pay special attention to nested configurations.
181181
</Callout>
182182

183183
If you have previously configured Amplify by passing the configuration object literal when calling the `Amplify.configure()` function, you can now configure Amplify manually with type safety. Please refer to the documentation of each category that you are using for migration.

0 commit comments

Comments
 (0)