-
Notifications
You must be signed in to change notification settings - Fork 275
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
#512: Changed from Set to List to store HTML node renderer handlers i… #514
base: master
Are you sure you want to change the base?
Conversation
…rs in a manner that preserves order. Added a test.
...main/java/com/vladsch/flexmark/html2md/converter/internal/HtmlConverterCoreNodeRenderer.java
Show resolved
Hide resolved
@SimonIT When running unit tests, I noticed that two tests fail in
|
I have no clue, I'm not familiar with this project in any way |
@vsch Any idea? |
@vsch Is there anything I can help with so that we can merge these changes? |
Can you please clarify for me what is the issue you are trying to resolve with ordering the HtmlNodeRendererHandler set? All renderer and parser handlers are sets because all are extendable, can be added in any order, with only their dependencies dictating the order of their application. Otherwise, the order in which they are added will become a nightmare for users to figure out and maintain. In this case, the invocation of HTML node renderer is dictated by resolving its jsoup node class and tag. If there are non-unique overlaps, then dependency declaration methods have to be added to As far as the DocX testSpecExample[Emoji: 4], and also testSpecExample[Emoji: 3] tests, I disabled those tests in the next release because the image urls are no longer valid. My website and associated Amazon S3 are no more, $1000+/yr to Amazon was more than I could justify or afford. Once I have gone through the backlog of issues, I will go back and resolve these tests with more stable and available URLs. |
…n a manner that preserves order. Added a test.