feat(amplify_core): initial commit for amplify-flutter #2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Amplifiyer
reviewed
Jun 25, 2020
..._core/android/src/main/kotlin/com/amplifyframework/flutter/amplify_core/AmplifyCorePlugin.kt
Outdated
Show resolved
Hide resolved
..._core/android/src/main/kotlin/com/amplifyframework/flutter/amplify_core/AmplifyCorePlugin.kt
Outdated
Show resolved
Hide resolved
..._core/android/src/main/kotlin/com/amplifyframework/flutter/amplify_core/AmplifyCorePlugin.kt
Outdated
Show resolved
Hide resolved
added 2 commits
June 25, 2020 08:51
Amplifiyer
approved these changes
Jun 30, 2020
haverchuck
changed the title
HuiSF
referenced
this pull request
in HuiSF/amplify-flutter
Jun 2, 2021
feat(datastore) Allow configure DataStore with custom configuration
9 tasks
9 tasks
dnys1
added a commit
that referenced
this pull request
Jul 22, 2022
Before ``` flutter: ERROR | SignUpStateMachine | Emitted error flutter: ERROR | Authenticator | Error in AuthBloc ``` After ``` flutter: ERROR | SignUpStateMachine | Emitted error: InvalidParameterException [Attributes did not conform to the schema: email: The attribute is required, null, null] #0 HttpOperation.deserializeOutput package:smithy/…/http/http_operation.dart:278 <asynchronous suspension> #1 AWSRetryer.retry package:smithy_aws/…/retry/aws_retryer.dart:160 <asynchronous suspension> #2 WrappedCognitoIdentityProviderClient.signUp package:amplify_auth_cognito_dart/…/sdk/sdk_bridge.dart:516 <asynchronous suspension> #3 SignUpStateMachine.onInitiate package:amplify_auth_cognito_dart/…/machines/sign_up_state_machine.dart:42 <asynchronous suspension> #4 SignUpStateMachineBase.resolve package:amplify_auth_cognito_dart/…/generated/sign_up_state_machine_base.dart:39 <asynchronous suspension> #5 StateMachine._listenForEvents package:amplify_core/…/state_machine/state_machine.dart:171 <asynchronous suspension> flutter: ERROR | Authenticator | Error in AuthBloc: InvalidParameterException [Attributes did not conform to the schema: email: The attribute is required, null, null] ```
13 tasks
13 tasks
13 tasks
13 tasks
dnys1
pushed a commit
that referenced
this pull request
Feb 22, 2023
Errors originating within state machines lose context when thrown since there is an asynchronous gap between adding an event to a state machine and when it eventually gets processed. For example, consider the following exception thrown from a state machine: ``` ERROR | MyStateMachine | Emitted error: Exception #0 MyStateMachine.doWork (file:///Users/nydillon/dev/amplify-dart/packages/amplify_core/test/state_machine/my_state_machine.dart:82:7) <asynchronous suspension> #1 MyStateMachine.resolve (file:///Users/nydillon/dev/amplify-dart/packages/amplify_core/test/state_machine/my_state_machine.dart:100:9) <asynchronous suspension> #2 StateMachine._listenForEvents (package:amplify_core/src/state_machine/state_machine.dart:237:9) <asynchronous suspension> ``` The trace ends at `listenForEvents` in the state machine, which is where the event was popped off the internal queue. But what happened before? With chaining, we get the following which provides the whole picture: ``` ERROR | MyStateMachine | Emitted error: Exception test/state_machine/my_state_machine.dart 82:7 MyStateMachine.doWork test/state_machine/my_state_machine.dart 100:9 MyStateMachine.resolve package:amplify_core/src/state_machine/state_machine.dart 238:9 StateMachine._listenForEvents ===== asynchronous gap =========================== package:amplify_core/src/state_machine/event.dart 41:47 new EventCompleter package:amplify_core/src/state_machine/state_machine.dart 127:23 StateMachineManager.accept test/state_machine/state_machine_test.dart 47:30 main.<fn>.<fn> package:test_api/src/backend/declarer.dart 215:19 Declarer.test.<fn>.<fn> package:test_api/src/backend/declarer.dart 213:7 Declarer.test.<fn> package:test_api/src/backend/invoker.dart 258:9 Invoker._waitForOutstandingCallbacks.<fn> ``` Now we can see that the exception originated due to an event which was created by calling `StateMachineManager.accept` within a test. Much better!
dnys1
pushed a commit
that referenced
this pull request
Feb 22, 2023
Errors originating within state machines lose context when thrown since there is an asynchronous gap between adding an event to a state machine and when it eventually gets processed. For example, consider the following exception thrown from a state machine: ``` ERROR | MyStateMachine | Emitted error: Exception #0 MyStateMachine.doWork (file:///Users/nydillon/dev/amplify-dart/packages/amplify_core/test/state_machine/my_state_machine.dart:82:7) <asynchronous suspension> #1 MyStateMachine.resolve (file:///Users/nydillon/dev/amplify-dart/packages/amplify_core/test/state_machine/my_state_machine.dart:100:9) <asynchronous suspension> #2 StateMachine._listenForEvents (package:amplify_core/src/state_machine/state_machine.dart:237:9) <asynchronous suspension> ``` The trace ends at `listenForEvents` in the state machine, which is where the event was popped off the internal queue. But what happened before? With chaining, we get the following which provides the whole picture: ``` ERROR | MyStateMachine | Emitted error: Exception test/state_machine/my_state_machine.dart 82:7 MyStateMachine.doWork test/state_machine/my_state_machine.dart 100:9 MyStateMachine.resolve package:amplify_core/src/state_machine/state_machine.dart 238:9 StateMachine._listenForEvents ===== asynchronous gap =========================== package:amplify_core/src/state_machine/event.dart 41:47 new EventCompleter package:amplify_core/src/state_machine/state_machine.dart 127:23 StateMachineManager.accept test/state_machine/state_machine_test.dart 47:30 main.<fn>.<fn> package:test_api/src/backend/declarer.dart 215:19 Declarer.test.<fn>.<fn> package:test_api/src/backend/declarer.dart 213:7 Declarer.test.<fn> package:test_api/src/backend/invoker.dart 258:9 Invoker._waitForOutstandingCallbacks.<fn> ``` Now we can see that the exception originated due to an event which was created by calling `StateMachineManager.accept` within a test. Much better!
dnys1
pushed a commit
that referenced
this pull request
Feb 22, 2023
Errors originating within state machines lose context when thrown since there is an asynchronous gap between adding an event to a state machine and when it eventually gets processed. For example, consider the following exception thrown from a state machine: ``` ERROR | MyStateMachine | Emitted error: Exception #0 MyStateMachine.doWork (file:///Users/nydillon/dev/amplify-dart/packages/amplify_core/test/state_machine/my_state_machine.dart:82:7) <asynchronous suspension> #1 MyStateMachine.resolve (file:///Users/nydillon/dev/amplify-dart/packages/amplify_core/test/state_machine/my_state_machine.dart:100:9) <asynchronous suspension> #2 StateMachine._listenForEvents (package:amplify_core/src/state_machine/state_machine.dart:237:9) <asynchronous suspension> ``` The trace ends at `listenForEvents` in the state machine, which is where the event was popped off the internal queue. But what happened before? With chaining, we get the following which provides the whole picture: ``` ERROR | MyStateMachine | Emitted error: Exception test/state_machine/my_state_machine.dart 82:7 MyStateMachine.doWork test/state_machine/my_state_machine.dart 100:9 MyStateMachine.resolve package:amplify_core/src/state_machine/state_machine.dart 238:9 StateMachine._listenForEvents ===== asynchronous gap =========================== package:amplify_core/src/state_machine/event.dart 41:47 new EventCompleter package:amplify_core/src/state_machine/state_machine.dart 127:23 StateMachineManager.accept test/state_machine/state_machine_test.dart 47:30 main.<fn>.<fn> package:test_api/src/backend/declarer.dart 215:19 Declarer.test.<fn>.<fn> package:test_api/src/backend/declarer.dart 213:7 Declarer.test.<fn> package:test_api/src/backend/invoker.dart 258:9 Invoker._waitForOutstandingCallbacks.<fn> ``` Now we can see that the exception originated due to an event which was created by calling `StateMachineManager.accept` within a test. Much better!
dnys1
pushed a commit
that referenced
this pull request
Feb 23, 2023
Errors originating within state machines lose context when thrown since there is an asynchronous gap between adding an event to a state machine and when it eventually gets processed. For example, consider the following exception thrown from a state machine: ``` ERROR | MyStateMachine | Emitted error: Exception #0 MyStateMachine.doWork (file:///Users/nydillon/dev/amplify-dart/packages/amplify_core/test/state_machine/my_state_machine.dart:82:7) <asynchronous suspension> #1 MyStateMachine.resolve (file:///Users/nydillon/dev/amplify-dart/packages/amplify_core/test/state_machine/my_state_machine.dart:100:9) <asynchronous suspension> #2 StateMachine._listenForEvents (package:amplify_core/src/state_machine/state_machine.dart:237:9) <asynchronous suspension> ``` The trace ends at `listenForEvents` in the state machine, which is where the event was popped off the internal queue. But what happened before? With chaining, we get the following which provides the whole picture: ``` ERROR | MyStateMachine | Emitted error: Exception test/state_machine/my_state_machine.dart 82:7 MyStateMachine.doWork test/state_machine/my_state_machine.dart 100:9 MyStateMachine.resolve package:amplify_core/src/state_machine/state_machine.dart 238:9 StateMachine._listenForEvents ===== asynchronous gap =========================== package:amplify_core/src/state_machine/event.dart 41:47 new EventCompleter package:amplify_core/src/state_machine/state_machine.dart 127:23 StateMachineManager.accept test/state_machine/state_machine_test.dart 47:30 main.<fn>.<fn> package:test_api/src/backend/declarer.dart 215:19 Declarer.test.<fn>.<fn> package:test_api/src/backend/declarer.dart 213:7 Declarer.test.<fn> package:test_api/src/backend/invoker.dart 258:9 Invoker._waitForOutstandingCallbacks.<fn> ``` Now we can see that the exception originated due to an event which was created by calling `StateMachineManager.accept` within a test. Much better!
dnys1
pushed a commit
that referenced
this pull request
Feb 23, 2023
Errors originating within state machines lose context when thrown since there is an asynchronous gap between adding an event to a state machine and when it eventually gets processed. For example, consider the following exception thrown from a state machine: ``` ERROR | MyStateMachine | Emitted error: Exception #0 MyStateMachine.doWork (file:///Users/nydillon/dev/amplify-dart/packages/amplify_core/test/state_machine/my_state_machine.dart:82:7) <asynchronous suspension> #1 MyStateMachine.resolve (file:///Users/nydillon/dev/amplify-dart/packages/amplify_core/test/state_machine/my_state_machine.dart:100:9) <asynchronous suspension> #2 StateMachine._listenForEvents (package:amplify_core/src/state_machine/state_machine.dart:237:9) <asynchronous suspension> ``` The trace ends at `listenForEvents` in the state machine, which is where the event was popped off the internal queue. But what happened before? With chaining, we get the following which provides the whole picture: ``` ERROR | MyStateMachine | Emitted error: Exception test/state_machine/my_state_machine.dart 82:7 MyStateMachine.doWork test/state_machine/my_state_machine.dart 100:9 MyStateMachine.resolve package:amplify_core/src/state_machine/state_machine.dart 238:9 StateMachine._listenForEvents ===== asynchronous gap =========================== package:amplify_core/src/state_machine/event.dart 41:47 new EventCompleter package:amplify_core/src/state_machine/state_machine.dart 127:23 StateMachineManager.accept test/state_machine/state_machine_test.dart 47:30 main.<fn>.<fn> package:test_api/src/backend/declarer.dart 215:19 Declarer.test.<fn>.<fn> package:test_api/src/backend/declarer.dart 213:7 Declarer.test.<fn> package:test_api/src/backend/invoker.dart 258:9 Invoker._waitForOutstandingCallbacks.<fn> ``` Now we can see that the exception originated due to an event which was created by calling `StateMachineManager.accept` within a test. Much better!
Closed
13 tasks
14 tasks
14 tasks
14 tasks
14 tasks
14 tasks
14 tasks
14 tasks
14 tasks
14 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of changes:
Initial commit for aws-amplify-flutter, including amplify_core and amplify_core_plugin_interface packages.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.