-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Evernote bug bounty - $300 #204
Comments
@akosbalasko let us know if you're interested in picking this up! |
Hi @kepano , |
Hi @kepano , According to the contribution description, here is my formal application to the bounty:
Thanks again! |
I have assigned the bounty to you. Please submit your initial PR by end of day February 6th. Let's start with the easiest and most obvious ones first. If you have any questions about requirements on specific issues please post them here. It sounds like we should consider ignoring #24 and #187, unless you can think of a way to support those? |
Hi @kepano , Regarding #24 and #187, I think there is a workaround to achieve the expected result, but it requires manual modification within Evernote: as enex doesn't contain neither the hierarchy of tags nor the notebook stacks, tags and notebook names could be "flat" out with some predefined delimiter, and we could use that property to store the full-path of the notebooks and tags respectively. But this must be done by the import within Evernote. The preferred delimiter could be highlighter in the documentation of the Importer. |
@akosbalasko please go ahead and get additional detail from the users on issues #184, #194, #201 For #24 and #187 it sounds acceptable, but can you start by writing a bullet point version of the documentation first? I don't use Evernote myself so I am not clear how the user would go about doing this. What would the steps be for the user to add the delimiter? You can reply here. |
@kepano , sure sure I'll start with the bullet points then. One other thing: during the implementations I realized that generating the title "inside" the note with header1 doesn't look good as the filename itself appears at the top. May/Should I remove it? And one more thing: How about unit tests? I don't see any around, shouldn't we introduce mocha for instance? |
Yes, we should remove the repeated H1 title. It's not necessary and it's also different from how all other Importer formats work. Later we can add a generic option for all import types to add an H1, since this isn't Evernote-specific. Regarding unit tests, I will leave this up to @lishid. I don't think it's necessary but he may disagree. In general we prefer to avoid external dependencies. |
I think we are ok to not have tests for now. Importer isn't really a moving target unlike a living and frequently updated app so I think it would be ok for now to keep it simple. We could include some test cases in the |
@kepano
in Evernote it should be renamed to tag1/tag2 . But in this case we solved everything as Obsidian is able to recognize nesting in tags with '/' as delimiter. So in case of tags I think the most what we can do is to extend the documentation with this hint: If you would like to keep nested tags, pls rename all of the tags with their fullpath respectively. And note that it is due to Evernotes bad implementation of tags. But the same trick can be used in case of #24 . Notebook stacks cannot be exported from Evernote at all, we can just export notebooks only. So, in order to keep the stack, the users must extend the exported enex file's name with its notebook stack's name with a delimiter.
Here is the steplist what is needed to do to handle notebookStacks:
Then the conversion could recognize this(split name by @@@), create the notestack folder and use that as basepath. |
@akosbalasko Yes, that makes sense to me. Go ahead. The tag notation seems intuitive enough. I don't have a strong opinion about the right delimiter for notebook stacks, what you have proposed sounds okay to me. |
Bounty
See the Contribution guidelines for how to claim this bounty.
Bounty: $300 USD
Timeframe: 10 days
Requirements
Bug bounty including the following Evernote bugs. Most of them are related to improper formatting, or missing conditions in file names.
The text was updated successfully, but these errors were encountered: