Skip to content

Patch parsing error messages #8

Open
@abhinav

Description

@abhinav

The machinery for parsing patches is currently convoluted, with multiple temporary files created inside token.FileSets so that when failures do occur, we have no obvious correlation to positions in the patch.

We should simplify that by not introducing these temporary file sets, or mapping positions back to the original patch file. Go syntax error messages should specify exact positions in the patch files.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions