Describe the bug
At the time of registration, email has not been validated correctly http://localhost:1337/admin/auth/register

Expected behavior
An email should be valid in all aspect like

• should check valid domain, well-formed and valid mailbox

Screenshots
invalid email1:

First check

• I added a very descriptive title to this issue.
• I used the GitHub search to find a similar issue and didn't find it.
• I searched the FastAPI documentation, with the integrated search.
• I already searched in Google "How to X in FastAPI" and didn't find any information.
• I already read and followed all the tutorial in the docs and didn't find an answ

Is there an existing issue for this?

• I have searched the existing issues

Summary

It would be amazing to have an Authorization tab on GraphQL, as it is for REST.

Why should this be worked on?

Authorization is also a thing in GQL and having automated OAuth mechanism would be 👍

Base64 packing the logo is unproductive and prohibitively complicated.

Originally I just thought it was related to the method of delivery, minification,etc....

But then I discovered the "enterprise" copy you sell directly offers the "feature" of changing the logo, which then just packs up a new image.

Now I realize why changing the logo is difficult and you won't document how to do it in

Bug Report Checklist

• [~] Have you provided a full/minimal spec to reproduce the issue?
• Have you validated the input using an OpenAPI validator, yes I used the validate function of the api generator
• [5.0.0 ] What's the version of OpenAPI Generator used?
• Have you search for related issues/PRs?
• What's the actual output vs expected output?

As discussed in #1979, the current CONTRIBUTING.md document instructs people to run tools/mintest.sh, which requires Python 3.8 and 3.5 installed simultaneously and then it makes things a bit confusing when referencing Python 3.6 or 3.7 and then pyenv shell 3.8.0 3.5.8 and then further below pyenv virtualenv 3.8.0 falcon-sandbox-38. I'm not familiar with pyenv, but this

For some reason Amazon REST api's require the content-type to be set to "application/x-amz-json-1.1" instead of the standard "application/json"

Currently the content-type header is set automatically for json data overriding any headers passed in to the request.

It would be useful to first check if the header is set before overriding it:

if (!this.request.headers.set('content-type')) {

https://github.com/kgrzybek/modular-monolith-with-ddd/blob/54d209639e501301e879aa0d0a84c9ea49e4689e/src/Modules/Meetings/Domain/Meetings/Rules/MeetingAttendeesLimitMustBeGreaterThanGuestsLimitRule.cs#L1-L21

I believe the comparison operator used in the IsBroken method is wrong because the rule is checking that meeting attendees limit must be greater than guests limit.

Issue

The response header does not reflect the correct version for HTTP2 requests. Even though, wiremock replies in h2 but the version in the response header shows "HTTP/1.1 200". This is caused by the hardcoded value in the toString() method of Response.java class

    @Override
    public String toString() {
        StringBuilder sb = new StringBuilder();
        **sb.append("HTTP