Skip to content

chore: add a warning if amplify configure has not been called #14424

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
Jun 18, 2025

Conversation

soberm
Copy link
Contributor

@soberm soberm commented Jun 10, 2025

Description of changes

The purpose of this PR is to add a warning if Amplify.configure() has not been called. This adds more context to errors resulting from missing configuration.

Issue #, if available

Description of how you validated changes

Checklist

  • PR description included
  • yarn test passes
  • Unit Tests are changed or added
  • Relevant documentation is changed or added (and PR referenced)

Checklist for repo maintainers

  • Verify E2E tests for existing workflows are working as expected or add E2E tests for newly added workflows
  • New source file paths included in this PR have been added to CODEOWNERS, if appropriate

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@soberm soberm marked this pull request as ready for review June 10, 2025 14:26
@soberm soberm merged commit 43e28a6 into main Jun 18, 2025
30 checks passed
@soberm soberm deleted the feat/config-warning branch June 18, 2025 08:17
Simone319 pushed a commit that referenced this pull request Jun 30, 2025
* chore: add a warning if amplify configure has not been called

* chore: adjust package size limits
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants