support recursive collection of source files for provider using fs.FS #706
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fmarmol
force-pushed
the
support_recursive_search_in_filesystem_for_new_provider_api
branch
from
cd26a9e
to
11ba682
Compare
fmarmol
force-pushed
the
support_recursive_search_in_filesystem_for_new_provider_api
branch
from
11ba682
to
9407563
Compare
|
Interesting, I'm curious to understand what problem this would solve? Is this related to #349 by any chance? |
|
Hi @mfridman Its not directly linked, but the problem is similar. In my case it was common migrations files compatible for postgresql and sqlite and specific folder for each database |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello,
Since its easy to add any subfolders in embed.FS, wanted to support collection of source files recursively for the new provider API using fs.FS. What do you think about this PR ?