Skip to content

Clarify rich text description of mention object #234

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.

Sign up for GitHub

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

Merged
merged 2 commits into from
May 23, 2025
Merged

Clarify rich text description of mention object #234

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
30fe2b8
Update rich text description to clarify ref type
tilenkavcic May 22, 2025
07fd85c
Update fern/docs/pages/airdrop/data-model/rich-text-fields.mdx
tilenkavcic May 23, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion fern/docs/pages/airdrop/data-model/rich-text-fields.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ Mention objects represents any mention (user, issue, etc.) in rich text and have
| Field | Type | Required | Description |
| ---------------------- | ------ | -------- | ------------------------------------------------------------------------------------------------------------------------------------ |
| `id` | String | Yes | Identifier of the mentioned item (user ID, etc.) in the format used by the source system. |
| `ref_type` | String | Yes | Type of the mentioned item (for example, "issue", "comment"). The recipe converts this based on user mappings. |
| `ref_type` | String | Yes | Type of the mentioned item (for example, "issue", "comment"). It should match the record type defined in external domain metadata. The recipe converts this based on user mappings. |
| `fallback_record_name` | String | No | Display text if the mention cannot be resolved (user display name, ticket title, etc.). |

In reverse, the loader should expect the following structure:
Expand Down
Loading