Skip to content

Bug in parser #7

Description

@sluongng

In case the file path is ended with /, you should not translate to ** but to * only

The differences between ** and * is that

  • /* match all the child files under that dir but NOT the sub directories
  • /** match all the child files AND sub directories (need a recursive parse)

Another issue is that this parser is not handling backtick \ characters.

If a file path has \ in front of a whitespace(Window), an @ or a #, it should still be valid file path

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions