Skip to content
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

support for styling ordered/unordered lists and list elements #109

Merged
merged 1 commit into from
Feb 28, 2022

Conversation

fire-oak
Copy link
Contributor

@fire-oak fire-oak commented Feb 28, 2022

<ul>, <ol> and <li> elements can now be styled with Word Document styles using the class attribute. an unstyled <li> elements inherits its styling from its parent list element (<ul> or <ol>).

example:

<ul class="CustomList">
    <li>...</li>
    <li class="AlternateListItem">...</li>
    <li>...</li>
</ul>

If CustomList matches a (Word) Document Style, this style will be applied to the paragraphs that are created for every <li> child element of the <ul> list tag. If the <li> element has a class that matches a (Word) Document Style, this inherited behaviour will be overwritten.

In the example above, the paragraph generated for the second <li> element will have the AlternateListItem style applied in Word, while the other two <li> elements will have the CustomList style applied, as inherited by their parent list tag.

<ul>, <ol> and <li> elements can now be styled using the class attribute. an unstyled <li> elements inherits its styling from its parent list element (<ul> or <ol>)
@onizet
Copy link
Owner

onizet commented Feb 28, 2022

Nice, thank you

@onizet onizet merged commit 41390d6 into onizet:dev Feb 28, 2022
@fire-oak
Copy link
Contributor Author

Oh that was quick. When will these changes be available on nuget? in other words, when will be the next release of this nuget package?

@onizet
Copy link
Owner

onizet commented Mar 2, 2022

it's done

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants