I've been looking at the current (new) implementation, and it seems to me that with one specific change, several issues could be started to be resolved.
The change I am talking about is switching from using the raw link of a given gist to using the Github API. If this switch was made, the all of the following issues could then be implemented:
Or, in other words, all of the issues above would require using the Github API.
I've made a first working draft with an example implementation. Please note that it is not pretty (I still need to clean it all up), it was mostly to get an idea of what you think.
(Feel free to ignore my example implementation and re-implement it any way you please).
You can see my code here: #112
I've been looking at the current (new) implementation, and it seems to me that with one specific change, several issues could be started to be resolved.
The change I am talking about is switching from using the
rawlink of a given gist to using the Github API. If this switch was made, the all of the following issues could then be implemented:Support multi-file gists which have one markdown file Support multi-file gists which have one markdown file #75Add author and date at the header Add author and date at the header #20Support private gists Support private gists #17Or, in other words, all of the issues above would require using the Github API.
I've made a first working draft with an example implementation. Please note that it is not pretty (I still need to clean it all up), it was mostly to get an idea of what you think.
(Feel free to ignore my example implementation and re-implement it any way you please).
You can see my code here: #112