I thougt it would make sense to keep them in.
I originally exported from Google Keep To Standard Notes and got these
escapes.
Also the debugging may help for some ... if you don't want them in your
code feel free to cut them out
Best,
Arne
On Tue, Jun 2, 2020, 18:18 Andros Fenollosa <notifications@github.com>
wrote:
> Could you remove the annotated code fragments?
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/tanrax/standard-notes-to-evernote-or-joplin/pull/4#issuecomment-637659412>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAB5GL6PUB3UDUBJGENLP5DRUUQ3XANCNFSM4NQ3AS3Q>
> .
>
@ArneTR It is not a good practice to leave commented code as it is not self-explanatory. For this, perhaps, it would be advisable to take it to README.md with some commentary. I would appreciate it if you would apply either of these actions :)
@ArneTR It is not a good practice to leave commented code as it is not self-explanatory. For this, perhaps, it would be advisable to take it to README.md with some commentary. I would appreciate it if you would apply either of these actions :)
tanrax
(Migrated from github.com)
reviewed 2020-06-03 17:08:20 +02:00
unclear what you mean by bad indentation ....? Maybe your editor got it wrong? Looks fine to me ...?
Anyhow, I closed the request and send you an new one.
Please have a look at it.
Also you can accept the pull-request and modify it afterwards if you want to have the code differently in your repo. Just wanted you to get the credit and keep it centralised
unclear what you mean by bad indentation ....? Maybe your editor got it wrong? Looks fine to me ...?
Anyhow, I closed the request and send you an new one.
Please have a look at it.
Also you can accept the pull-request and modify it afterwards if you want to have the code differently in your repo. Just wanted you to get the credit and keep it centralised
ArneTR
(Migrated from github.com)
reviewed 2020-06-04 16:01:30 +02:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Good job @ArneTR
Could you remove the annotated code fragments?
I thougt it would make sense to keep them in.
I originally exported from Google Keep To Standard Notes and got these
escapes.
Also the debugging may help for some ... if you don't want them in your
code feel free to cut them out
Best,
Arne
On Tue, Jun 2, 2020, 18:18 Andros Fenollosa notifications@github.com
wrote:
@ArneTR It is not a good practice to leave commented code as it is not self-explanatory. For this, perhaps, it would be advisable to take it to README.md with some commentary. I would appreciate it if you would apply either of these actions :)
@@ -47,3 +52,2 @@text = item['content']['text']text = text_from_html(title, text)text = item['content']['text']There's bad indentation.
@@ -47,3 +52,2 @@text = item['content']['text']text = text_from_html(title, text)text = item['content']['text']unclear what you mean by bad indentation ....? Maybe your editor got it wrong? Looks fine to me ...?
Anyhow, I closed the request and send you an new one.
Please have a look at it.
Also you can accept the pull-request and modify it afterwards if you want to have the code differently in your repo. Just wanted you to get the credit and keep it centralised
@@ -47,3 +52,2 @@text = item['content']['text']text = text_from_html(title, text)text = item['content']['text']sry, my bad. Saw it was just one space instead of usually 4. fixed
Pull request closed