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

fix: still try extensions even if it looks like it already has one #4

Merged
merged 1 commit into from
Aug 25, 2020

Conversation

emmachase
Copy link
Member

No description provided.

@emmachase emmachase requested a review from 1lann August 16, 2020 15:17
Copy link
Member

@1lann 1lann left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks fine to me, I think... my head is spinning though cause i'm kinda sick so my judgement might be off. idk maybe try thinking of some edge cases if they could cause a certain path being inaccessible or something, or a list of examples of old and new behaviour.

@emmachase
Copy link
Member Author

It always tries the exact requested path first, and only ever tries additional directories. So I cannot see any possible regressions.

@emmachase emmachase merged commit 98e65fa into master Aug 25, 2020
@emmachase emmachase deleted the emma/always-ext branch August 25, 2020 21:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants