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 paths not using mapping when scanning project #28

Merged
merged 2 commits into from
Feb 1, 2023

Conversation

raustin-m
Copy link
Contributor

Fixes #27

Paths were not being mapped when scanning a project the same way they were when scanning a single file. This PR fixes that by adding a method that returns a (synchronous) mapping function, which can then be used to map one or many paths using the same mapping config (retrieved asynchronously).

@SanderRonde
Copy link
Owner

Looks good! Maybe one thing based on your comment in the other thread is to make it so the getPathMapper function takes a inverse parameter that is true for the project-case. Then you won't need to put the reverse path mapping in the settings. Could you do that part too? Then it's all good.

@raustin-m
Copy link
Contributor Author

Sure thing, just added that and it seems to work fine with just the one entry in my paths config now.

@SanderRonde
Copy link
Owner

Awesome, thanks! I'll merge it

@SanderRonde SanderRonde merged commit c20537f into SanderRonde:master Feb 1, 2023
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.

"Scan project" does not respect path mapping
2 participants