Recent searches
No recent searches
![Christopher Kennedy's Avatar](https://secure.gravatar.com/avatar/85d97d7b254087e7d6bc7d30caf85255?default=https%3A%2F%2Fassets.zendesk.com%2Fhc%2Fassets%2Fdefault_avatar.png&r=g)
Christopher Kennedy
Joined Apr 14, 2021
·
Last activity Feb 06, 2025
Following
0
Followers
3
Total activity
801
Votes
0
Subscriptions
337
ACTIVITY OVERVIEW
BADGES
ARTICLES
POSTS
COMMUNITY COMMENTS
ARTICLE COMMENTS
ACTIVITY OVERVIEW
Latest activity by Christopher Kennedy
Christopher Kennedy commented,
Can you share the conditions for when you currently perform the redaction?
View comment · Posted Feb 06, 2025 · Christopher Kennedy
0
Followers
0
Votes
0
Comments
Christopher Kennedy commented,
0
Followers
0
Votes
0
Comments
Christopher Kennedy commented,
View comment · Posted Jan 28, 2025 · Christopher Kennedy
0
Followers
0
Votes
0
Comments
Christopher Kennedy commented,
I see you have a ticket open about this. I'm going to take that ticket over to work through this issue with you directly.
View comment · Posted Jan 28, 2025 · Christopher Kennedy
0
Followers
0
Votes
0
Comments
Christopher Kennedy commented,
Can you share some more context:
- Are you building a server-side Zendesk app? Or client-side app?
- How are you including MSAL? And how are you detecting that it's failing to initialize?
View comment · Posted Dec 20, 2024 · Christopher Kennedy
0
Followers
0
Votes
0
Comments
Christopher Kennedy commented,
0
Followers
0
Votes
0
Comments
Christopher Kennedy commented,
You can actually include HTML links in the value when using
ticket.editor.insert
. However, whether or not it is supported depends on the ticket channel. Live channels like chat and messaging do not support rich text replies, while other channels (web form, email, etc) do. That's really what accounts for the discrepancy in behavior that you're seeing. You can always use the ticket.editor.capabilities object to check whether the current channel supports rich text before performing the insert.View comment · Posted Dec 18, 2024 · Christopher Kennedy
0
Followers
0
Votes
0
Comments
Christopher Kennedy commented,
Hi Simon,
Thanks for the context. Sorry for the missed reply! Since you're just building an article excerpt, the simplest approach is to just pull the text from the returned article JSON body. This is easier to accomplish in vanilla JS using DOMParser() and innerText. For example, where you're currently sanitizing HTML:
let parser = new DOMParser();
let doc = parser.parseFromString(html, "text/html");
let text = doc.body.innerText;
return text;
This would return just the article body text without having to first load the body content, images, etc to the DOM before sanitizing.
Also to limit the number of articles returned by your API request, take advantage of pagination to set the max article count in the response to 6. For example:
const url = `${hcUrl}/api/v2/help_center/sections/${sectionId}/articles.json?page[size]=6`;
View comment · Posted Dec 05, 2024 · Christopher Kennedy
0
Followers
0
Votes
0
Comments
Christopher Kennedy commented,
I've created a ticket to work through this issue with you one-on-one. Please look out for my follow-up message from that ticket.
View comment · Posted Dec 04, 2024 · Christopher Kennedy
0
Followers
0
Votes
0
Comments
Christopher Kennedy commented,
Thanks for pointing this out. To sort when using cursor-based pagination use the
sort
parameter instead:{{baseUrl}}/api/v2/requests.json?page[size]=5&sort=updated_at
We detail this in Comparing cursor pagination and offset pagination, but we need to make it more clear in the endpoint specific docs.
View comment · Posted Nov 27, 2024 · Christopher Kennedy
0
Followers
0
Votes
0
Comments