Release/v3.1.10 by jgebal · Pull Request #1048 · utPLSQL/utPLSQL

Now it's published into main utplsql.gihub.io repository.

We need to make sure to calculate the corrent %endcontext annotation, not just the first that is greater than the next nested %context.
To operate correctly during recursion we also need information about the parent %endcontext position

Fixes #1034

Using simple parenthesis counter and annotations_by_line

Bugfix/nested context mixup

Now the validation is executed at runtime, when the tests is executed.

This resolves issues related to the fact that some package constants may not exist or be valid at suite parse time.
In such scenario, the annotations continued to be ignored despite the fact that package constants were valid at test runtime.

With this change, tests can now have `--throws` annotations referencing constants that are undefined at compile time.
Resolves #1033

Updated tests o represent the issue more clearly.

Closes #880

…arsing

Moved validation of `--%throws` annotation values.

…ace_vs_null_compare

Updated documentation for whitespace vs null compare.

Changed ordering of tests for suites with context

With this change the reporting of differences is unified across:
`unordered`, `ordered` and `join_by` comparison.

… available as part of `utPLSQL-cli` since version `3.1.8`

We do not use it since we switched to `small` databases.

Added ability to refresh annotation cache with DDL trigger enabled if schema was not full-scanned.
Resolves: #975

…trigger.

Fixed issues found while testing the code.

…g_fix

Fixed Teamcity reporting of errors

…havior

Refactored expectations on compound data

Cleanup and refactoring of annotation cache.