You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hiya, I was wondering if this project has a place for wrapping some file-related information.
Now, I forked this repository and added wrapping for a given file's URL, but I was wondering if this sort of functionality has enough merit and reason to add to the main project before I create a pull request.
I haven't added any tests yet, but if it'll be okay I'll go ahead and add some.
Thank you 🙂
The text was updated successfully, but these errors were encountered:
I do think there is a place for file support in the base library. I would like to figure out how best to incorporate files into the library.
Some thoughts on the code you linked:
What are you hoping to get out of the files? Just a listing of available files on the page?
Is there a reason that a new class is needed? If so, I don't think we would need to base the mediawikifile class on the mediawikipage class but I haven't had time to think it through in-depth.
Would it be easier to have a boolean property to say that the page is a file?
In non-english versions, is the term that signals the page is a file always File:? I know that for categories it can be other words/terms/etc.
Thanks for starting this discussion. I am excited to see where this goes!
Hiya, I was wondering if this project has a place for wrapping some file-related information.
Now, I forked this repository and added wrapping for a given file's URL, but I was wondering if this sort of functionality has enough merit and reason to add to the main project before I create a pull request.
I haven't added any tests yet, but if it'll be okay I'll go ahead and add some.
Thank you 🙂
The text was updated successfully, but these errors were encountered: