Skip to content

Support the byteOffset/charOffset from Region object for replacements #17

@kgevorkyan

Description

@kgevorkyan

Sarif supports several options for identify the place of warning/fixes via Region object:

  1. By indicating the lines and columns
  2. By indicating the byteOffset/charOffset and byteLength/charLength

For now we expect only lines and columns for indicating fix object, but it probably necessary to support byte offsets too

See https://docs.oasis-open.org/sarif/sarif/v2.1.0/os/sarif-v2.1.0-os.html#_Toc34317889

Under this issue we probably can introduce introduce our own model here. And make differences on class level: ReplacementByLine, ReplacementByOffset and etc., as suggested by @nulls

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions