-
Notifications
You must be signed in to change notification settings - Fork 7
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
Improve documentation #134
Comments
Hi @emmanuelHa - can you elaborate on the compilation error you're seeing?
|
Yes now I know that SignedInContent is "just" a placeholder. But for newcomers that's not what they want. They want something that allow a use case to work from end to end, copy paste a bit of code, test it and then they adapt this code. That' a a simple rule for coding: always quickly loop through code and test. By the way this code does not compile simply because this SignedInContent does not exist.
Is that ok for you ? |
Thanks for the suggestion @emmanuelHa. I'll update the documentation accordingly. |
Thanks @mattcreaser ! |
This issue is now closed. Comments on closed issues are hard for our team to see. |
Before opening, please confirm:
Which UI component is this feature-request for?
Authenticator
Please include any relevant guides or documentation you're referencing
https://ui.docs.amplify.aws/android/connected-components/authenticator/configuration
Please describe your feature-request in detail.
In the parent page (https://ui.docs.amplify.aws/android/connected-components/authenticator), it is written to add the following snipet:
`class MainActivity : ComponentActivity() {
override fun onCreate(savedInstanceState: Bundle?) {
super.onCreate(savedInstanceState)
SignedInContent ? This code does not compile.
When this feature is done with javascript the ui component woks out of the box.
I am expecting from such a common feature as Signin/Signup workflow a simple code to copy/paste.
Initialization steps (if applicable)
No response
Code Snippet
// Put your code below this line.
amplifyconfiguration.json
No response
Additional information and screenshots
No response
The text was updated successfully, but these errors were encountered: