That's a great question! 🙌 This is a link to our Amplify community on Discord as they may be able to give you further guidance on this: go.aws/amplify-discord. 🔗 Additionally, you can review the description for more links that may also assist. 💻 ^KR
Hello! I found this link in the description, you may find helpful: go.aws/3TQN3LI. You can find more information about Amplify Gen 2 here: go.aws/3TQN42e. If you have additional questions, feel free to email our Amplify team at aws-amplify-customer@amazon.com. ✅ ^MO
If I divide my amplify project into Separate frontend and backend repos, the frontend repo(next js) doesn't have access to the server-side amplify folder, which contains the backend schema. However, to achieve end-to-end type safety, generateClient needs the schema type. Is there any way to get types without accessing the Amplify data schema?
Sorry to hear about this frustration! Feel free to connect with our Amplify team over at Discord: go.aws/amplify-discord. 👈 Additionally, you can reach out to our community of experts over at re:Post for guidance: go.aws/aws-repost. ✅ ^AK
Sorry to hear that. 😔 Unfortunately, we don't have any insight into that discord server. You could also try our re:Post community of experts as they're always keen to share their knowledge: go.aws/aws-repost. 🤓 If you'd like to chat to our engineers directly, feel free to reach out to them via a support case through your Support Center: go.aws/support-center. 🛠️ ^RF
Hi, there. I have reached out internally to investigate your question. 🔎 For any other Amplify related concerns, please reach out via email: aws-amplify-customer@amazon.com. ✍️ To engage with the Amplify community, join the Discord channel through this link: go.aws/3uzpcFP. 🔗 ^ZP
