GQL framework

[renetapopova]

No description provided.

[renetapopova]

Comments from Gowri:

• The first lines in the ‘Server errors page’ mention that the GQL information is shown via driver and then we mention ‘Starting from version 5.25’ this is exposed to users. Only the Query.log changes are exposed from 5.25, the driver changes will be seen only from 5.26. - DONE
• ‘Starting from version 5.25, the Neo4j error codes have an additional GQL-status object’ can we change this to ‘Starting from version 5.25, the Neo4j error codes have an additional GQL-status object along with legacy errors’ .This is just to be a bit more explicit. - DONE
• Under ‘Classes of GQLSTATUS error codes’ section, you mentioned that Neo4j subclass starts N. Can we add a sentence to mention that any subclass not starting with N is a standard code. - DONE
• The topic ‘Server error classification’ is after the section, Legacy errors. As we are talking about the GQLSTATUS object classifications, do we want to move this before the Legacy errors heading? - The classification covers both GQLSTATUS and Neo4j Status errors, so that's why it follows both "object" sections.
• Under topic ‘Error internals’, we are talking about driver emitting GQL information. Do we change ‘Starting from 5.25,’ to ‘Starting from 5.26’? - Need to check with Louise on this/
• Topic ‘Query logging’, the default GQL codes highlighted in green , need to be at the top of the page. This way this can be the same for both drivers and Query.log. - I don't understand what this refers to.
• Topic ‘Server-driver version compatibility’ - There is a link to bolt and server compatibility. We need to mention from which bolt and Driver version, does the users get the additive GQL information. More like the table Louise Berglund has in her technical documentation. I really like the ‘Server-driver version compatibility’ for notifications. We can take inspiration from here too. - This section hasn't been written yet. It's just a placeholder for Louise.
• Status description explanation mentions class subclass and message in ‘Server errors’ page. One example in the next page ‘List of GQL status error codes’ is Status description error: connection exception - transaction resolution unknown. Will it help to include a format like error: class - subclass. Message in the explanation section? We do say that with different words: "A human-readable description of the GQLSTATUS, which consists of a condition, a subcondition, and a description.
  The condition and subcondition are textual representations of the class and subclass codes, respectively." I am not sure what your suggestion is here.

[Lojjs]

A lot of feedback coming here. Feel free to first fix easy stuff and then give me a call to discuss or whatever you find easiest.

[Lojjs]

Thanks for all the hard work on this one 👏

[hvub]

This looks all pretty good. All the comments are just little things I noticed while reading. Feel free to do with that as you see fit. :-)

[neo-technology-commit-status-publisher]

Thanks for the documentation updates.

The preview documentation has now been torn down - reopening this PR will republish it.