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
However, maybe it might be a good idea to create an abstract class like we did in the BASC-Archiver, which defines a standard interface with default functions that is extended and overrided by py4chan or py8chan.
That way, most of the code to generate attributes can be shared, while special features of a website (such as 8chan's multiple images on one post) can also be supported with a few overrides.
The text was updated successfully, but these errors were encountered:
It looks like with py8chan, I have abandoned the idea of direct inheritance from py4chan (because 4chan's API stands to diverge, and 8chan will be moving to Infinity-Next). When 4chan's API shifts, that would have an effect on all the others, which often rarely change.
For now, we're just going to fork the wrapper each time and adapt it to new chans whenever necessary.
Since I am going to try and create py8chan and py420chan wrapper classes (since their APIs were based on 4chan's API), I have been refactoring the BASC-py4chan wrapper to make it more extendable.
However, maybe it might be a good idea to create an abstract class like we did in the BASC-Archiver, which defines a standard interface with default functions that is extended and overrided by py4chan or py8chan.
That way, most of the code to generate attributes can be shared, while special features of a website (such as 8chan's multiple images on one post) can also be supported with a few overrides.
The text was updated successfully, but these errors were encountered: