nico-izo / kobato Goto Github PK

Since we have API, there's no need in it.

• Wait for methods in API
• Implement in KobatoApi
• Implement in posts/comments

• edit posts
• edit comments
• optional difftool

Current implementation tries to merge argument-based tags and stdin tags using set(). There is no reason for that (although now point allows multiple same tags, but it is a confirmed bug).

Subj.

This includes:

• Check that mentioned users exists on point
• Check markdown syntax (or at least preview/preview in browser)

• No tests
• Cannot specify dir (well, that's why no tests)
• Should not use operator[] and instead of that implement, hmm, set().

Subj.

As far as I can see it's the only blocker towards python 3.4 and 3.3 support.

Subj

Instead of doing some mock stuff with return values of json()

https://pypi.python.org/pypi/requests-mock

This feature cannot be implemented now due to missing methods in point.im api.
So...

• Wait for arts/someone who will implement that in public API
• Implement in KobatoApi
• Implement in KobatoSubscribe

Subj.

subj.

https://docs.python.org/3/library/unittest.mock.html#unittest.mock.MagicMock

There are some examples:

Subj

According to this: https://github.com/artss/point-doc/pull/9

• /all
• edit comment
• view bookmarks
• blacklisters
• login
• ulogin (like wtf, entire API and still no login)

Current implementation of draft parser disallows user from using tags with commas.

Everyone have their own tag structure/policy in their blogs.

And sometimes you can forgot about one or two.

Example:
*hoi4 -> *games

so message with only one tag *hoi4 automatically becomes *hoi4, games