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.

Sign up for GitHub

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

Jump to bottom

Paths not resolved #157

Closed
stevenvachon opened this issue Feb 13, 2019 · 1 comment
Closed

Paths not resolved #157

stevenvachon opened this issue Feb 13, 2019 · 1 comment
Assignees
@mrmlnc
Labels
Type: Bug
Milestone
2.2.7

Comments

@stevenvachon
Copy link

stevenvachon commented Feb 13, 2019 •
edited

Environment

  • OS Version macOS 10.14.2
  • Node.js Version: 10.15.0

Actual behavior

Paths are not resolved, with and without enabling the absolute option.

Expected behavior

Paths should have "." and ".." instances resolved.

Code sample

const paths = await fg('/project/temp/../*.js', {absolute: true});

console.log(paths[0]); //-> '/project/temp/../file.js'
@mrmlnc mrmlnc self-assigned this Feb 14, 2019
@mrmlnc mrmlnc pinned this issue Feb 20, 2019
@mrmlnc mrmlnc mentioned this issue May 12, 2019
Merged
@mrmlnc mrmlnc mentioned this issue May 12, 2019
Closed
13 tasks
@mrmlnc
Copy link
Owner

mrmlnc commented May 13, 2019

This issue will be fixed with release fast-glob@2.2.7. You can check release issue #180.

@mrmlnc mrmlnc closed this as completed May 13, 2019
@mrmlnc mrmlnc unpinned this issue May 13, 2019
@mrmlnc mrmlnc added this to the 2.2.7 milestone May 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mrmlnc mrmlnc

Labels
Type: Bug
Projects
None yet
Milestone
2.2.7
Development

No branches or pull requests
2 participants
@stevenvachon @mrmlnc