-
Notifications
You must be signed in to change notification settings - Fork 13
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
Scan filesystem #19
Comments
I think, there are two option for structure for correct parsing:
I'm suggesting second one. If there'll be an agreement on this, i will try to implement. |
Just thought about it a little bit more and I believe there are some other valid approaches we could take to make it as easy as possible for the user, but it depends on how complicated we what to make the implementation. We could load/add a list of series and let the user add a name, to cover both of your scenarios. We could also let the user choose the/a pattern (the two you suggested or something else). Weirdly enough for when I worked on something similar I structure my library to fit both patterns. |
I tried few things and reach this far:
If it's okay for you, maybe i would make a PR and then talk on it. |
ES6/7 (whatever works in the current version of node) is fine. For further discussion, a PR would be great. |
Write a function that accepts a file path and a list of extensions as a parameter and returns a list of found video files including additional information which can be extracted from the Filesystem.
e.g.
We should also research if we can extract additional information from the video file itself. Requiring a specific file structure may be a problem for users.
The text was updated successfully, but these errors were encountered: