Split the class `Quora` into `User` and `Question`

[csu]

Split the class `Quora` into `User` and `Question`

[csu]

I think we should have an Answer class as well. I was thinking classes for user, answer, question, topic, and activity.

On Wed, Dec 24, 2014 at 5:02 PM, Rohith PR [email protected]
wrote:

Or some other name instead of Question, this class will be responsible for questions and answers.

Reply to this email directly or view it on GitHub:
#39

[rohithpr]

Activity as in?

[csu]

User activity. Like their recent upvotes, follows, etc.

On Wed, Dec 24, 2014 at 5:07 PM, Rohith PR [email protected]
wrote:

Activity as in?

Reply to this email directly or view it on GitHub:
#39 (comment)

[rohithpr]

That'd be a part of the User class itself right?

[csu]

Yeah, like a subclass, but still a class of its own.

On Wed, Dec 24, 2014 at 5:10 PM, Rohith PR [email protected]
wrote:

That'd be a part of the User class itself right?

Reply to this email directly or view it on GitHub:
#39 (comment)

[rohithpr]

I'm yet to figure out what is going on in those "rss" functions so I'm not really in a position to talk about it.
Wouldn't it be better if everything related to a user i.e. stats, followers, followed by, answers and questions could all be in one place?

[csu]

Yes, but we can still organize those into subclasses of User. 

You can try using the activity endpoints on quora-api.

On Wed, Dec 24, 2014 at 5:15 PM, Rohith PR [email protected]
wrote:

I'm yet to figure out what is going on in those "rss" functions so I'm not really in a position to talk about it.

Wouldn't it be better if everything related to a user i.e. stats, followers, followed by, answers and questions could all be in one place?

Reply to this email directly or view it on GitHub:
#39 (comment)

[rohithpr]

Hmm.. That'll probably do it.

Sure, I'll take a look at it.

[csu]

This is a duplicate of #26 and #27