Berend de Boer

Regardless whether it is allowed, it's pretty common! All browsers handle it. I would say html-parser probably should not try to be a validating parser, that's an entirely different thing....

Secondly if the output comes via XML (XHTML 5.0), this could easily be generated. I.e. it's perfectly valid xml.

0.2.3. With simple schemes I can't repeat it either. But I can with the attached scheme: ``` node_modules/graphql-schema-linter/lib/cli.js tmp.graphql ``` See attached file: [graphql.txt](https://github.com/cjoudrey/graphql-schema-linter/files/4125733/graphql.txt)

Just tried 0.2.4, same crash.

I don't think you can remap just modifier keys. The latest Mac OS allows you to do that via its settings somewhat better than before, but not as fine-grained as...

Hi @jackielii, I had looked at your solution, and whatever I tried, it didn't work for me. Your response made me have another go, and working perfectly now. Thank you...

I just added the relevant bits of the CloudFormation template to the `amplify/backend/hosting/S3AndCloudFront/template.json` and that works fine. We already had a lambda@edge function doing path rewrites/redirects, so we just added...

@akr4 how exactly does this work? Prerender needs to visit the site without CloudFront doing any caching. I can't see how Cache-Control would help here, that's nice when returning data...

Ah, I think I understand how this could work: on viewer-request check if the user-agent is "Prerender". In that case you should make sure a cached version is never returned....

I just noticed that a lot of the comments here are also covered [in the v3 documentation](https://docs.aws.amazon.com/sdk-for-javascript/v3/developer-guide/s3-example-creating-buckets.html), see section "Getting a file from an Amazon S3 bucket".