Refactor the code to make it easier to extend and add features later about pymediawiki HOT 7 OPEN

That was just to illustrate. And I did not mean interfaces in Java, that was used as a general term.

from pymediawiki.

WikiPage class will have all the attributes you can think of for a single wiki page for example, make a list for categories, one for images, one for links etc. See from the MediaWiki API mentioned in README

from pymediawiki.

I'm taking this up next.
@abinashmeher999 Can you tell what kind of features/extensions should I expect will be added later?

from pymediawiki.

We are expecting to integrate all the properties of MediaWikiAPI for example links, categories, contributors, linkshere, images etc. The link to the API docs is given in README.

from pymediawiki.

Alright, and just to be clear, when you say

Make an interface with WikiPage class

are you referring to interfaces as in Java?

from pymediawiki.

So I tried refactoring and I find that the main WikiPage class does not have much in common with the new properties that we aim to add. In the end, I have just following attributes left in the WikiPage class - base_url, action, pageids, format.

Also, we need to parse JSON from every property differently, so the __res_cat_list and __strip_cat_item methods are not very useful too.

from pymediawiki.

Feel free to get rid of the methods if you think they won't be of much use.

from pymediawiki.