Rene Brandel

We should also make sure we handle dependencies like existence of docker & swift etc. These dependencies should be documented here: https://docs.amplify.aws/cli/function#supported-lambda-runtimes

hi @jaga810 - while the configurable parameters approach is backwards compatible in v2, we have opened up a more flexible approach to override the settings via `amplify override api` https://docs.amplify.aws/cli/graphql/override/...

We are using react-virtualized to visualize the data browser in our GraphQL Backend-as-a-Service. Since www.graph.cool could potentially serve millions of data items we need a UI that can scale as...

Thanks Tyler for the quick response. > you’ll probably want to get the raw AXUIElement from Swindler and look for child elements with that role Is there a way to...

We’ve recently launched sync expressions and are working on improvements now that we have more feedback from customers (like everyone on this thread). Over the next few months, we’re spending...

It'll depend on the scenarios itself. For offline-first applications, we do recommend DataStore as it provides many out-of-the-box benefits without manually configuring caching logic. AppSync Client SDK might be a...

Transferring to the Hosting console, as these are screenshots from the Hosting console's "detail page"

Transferring this to the Console repo because even though the title says "CloudFront", the description is specifically talking about Hosting.

Closing this issue because it's handled by-default with the server-side subscription filtering experience. https://docs.amplify.aws/cli/graphql/data-modeling/#server-side-filtering-for-subscriptions

Hi - I'm closing this issue because we're deprecating the existing workflow in favor of a new experience as part of the new GraphQL Transformer. You can follow along our...