Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

3.38.3 location property example includes "message" in the wrong place #410

Closed
lcartey opened this issue May 14, 2019 · 0 comments
Closed
Labels
bug impact-documentation-only merged Changes merged into provisional draft. non-substantive Change falls under editorial discretion resolved-fixed

Comments

@lcartey
Copy link

lcartey commented May 14, 2019

3.38.3 location property has the following example, where the message property is in the wrong place (it is on the threadFlowLocation object rather than the location object).

"locations": [
        ...
        {
          "executionOrder": 2,
          "message": {
            "text": "Attempt to write to the file."
          },
          "location": {
            "physicalLocation": {
              "artifactLocation": {
                "uri": "io/logger.c",
                "uriBaseId": "SRCROOT"
              },
              "region": {
                "startLine": 42,
                "snippet": {
                  "text": "    fprintf(fd, "test\\n");"
                }
              }
            }
          }
        }
@ghost ghost added bug non-substantive Change falls under editorial discretion impact-documentation-only resolved-fixed labels May 14, 2019
@ghost ghost self-assigned this May 15, 2019
@ghost ghost added the merged Changes merged into provisional draft. label May 20, 2019
@ghost ghost closed this as completed May 20, 2019
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug impact-documentation-only merged Changes merged into provisional draft. non-substantive Change falls under editorial discretion resolved-fixed
Projects
None yet
Development

No branches or pull requests

1 participant