Open arturtamborski opened 3 years ago
I want this library to be fast and in order to have that I would need to profile the library API.
I don't want to do it now because the API is not stable yet and I have more important things on my mind but that's a nice goal to have in the future.
Looks like Jamie merged some of the pull requests in the original repo which is nice :) It's good to know that he might still want to work on it further. I suppose we can expect a release shortly as well.
Update; I've sent some commits which are supposed to clean up the lib just a bit more (especially the conversion from notion to python and vice versa) which are working quite nicely though they still need a bit of work (still working on the details).
I plan to go back to the callback issue next (#40). After that I will create more smoke tests (hopefully at least a few for every block type) and then finally release the lib at v1.0.0
so that I can start working on the actual features.
I'm also back from short vacations in Berlin :) It's a really cool place to visit for the weekend, I can highly recommend it!
New release, v0.0.6 :) Lots of changes, but no major features for the user yet, I feel like I'm on the last turn (refactor of markdown and fix for callbacks) and then I'll be happy to work on Inline blocks or anything that's in features board.
I'm still experimenting with the look of release notes, I'm thinking about automating it from commits.
https://github.com/arturtamborski/notion-py/releases/tag/v0.0.6
Another update: I'm still working on https://github.com/arturtamborski/notion-py/issues/40 but it's much more difficult than I thought. This thing is weird. It uses some kind of prefixed json encoding thing for data and relies on websockets as well as regular requests. I only started figuring out the websocket thingy which supposedly uses https://github.com/primus/primus, which might come in handy.
Heyy, github introduced discussions! I might close this one when the new feature comes out of closed beta, will see. Here's an live example: https://github.com/servo/servo/discussions
Good resource for getting ideas of what exactly is still not implemented: https://www.notion.so/Help-Support-e040febf70a94950b8620e6f00005004 as well as this one: https://www.notion.so/What-s-New-157765353f2c4705bd45474e5ba8b46c
I've enabled discussions - they're available here: https://github.com/arturtamborski/notion-py/discussions
This ticket is for having a quick, random and open discussion on anything that relates to
notion
,notion-py
andnotion.so
.You can treat it as an IRC log / project "blog" in form of a Github issue :)
I will pick highly rated or interesting ideas from conversation and copy them over here or create a separate issue.
Click here to read more about the purpose of this ticket
It should be treated as an old-style multi-page overly-lengthy forum thread containing list of not-fully-refined ideas to implement. It's a place to share your feedback and opinions openly (but please keep your posts related to notion-py/notion.so). It's also an online substitute of the TODO.md file. Please note that it's just an experiment. I don't know if this will work out, especially since there aren't that many people around here anyway, but it's an idea that I wanted to try out and see how it ends up.The Grand List of Things includes: