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

Export Content API does not have the option to export Rich Text Elements as plain text #2763

Open
BryanValverdeU opened this issue Aug 7, 2024 · 1 comment

Comments

@BryanValverdeU
Copy link
Contributor

BryanValverdeU commented Aug 7, 2024

Describe the bug
Rich text elements are lost when exporting content as plain text

To Reproduce
Steps to reproduce the behavior:

  1. Go to demo site
  2. Create a table or a list
  3. Export the content as plain text

Expected behavior
The exported content should contain a plain text representation of the rich text elements or allow the exportContent API to allow extensability to support how the rich text elements should be represented in Plain text

Screenshots
Content to be exported:
image

Result:
image

Expectation:

1. 123123
2. 123213
3. 213213
...

Additional context
Current implementation should not change, but should be extendable to support this.

@BryanValverdeU BryanValverdeU changed the title Export Content API does not have the option to export Rich Text Elements Export Content API does not have the option to export Rich Text Elements as plain text Aug 7, 2024
@romanisa
Copy link
Contributor

romanisa commented Sep 9, 2024

Encouraged open-source contribution from the AddIns team within Microsoft, where this ask came from.

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

No branches or pull requests

2 participants