comments collection, so a comment isn’t an edit of the record: it writes no audit entry or version, and commenters don’t need update access.
Installation
Configuration
collections gets a comments field at the end of its fields. The plugin runs with order: 95, after plugins that add collections or fields.
Placing the field
commentsField() returns a normal ui field. Place it yourself and the collection needs no collections entry. It works alone anywhere in fields, or in a tab, for example next to the audit log’s activityField():
activityField() alone and leave this plugin out. Either field shows its label as a heading, except when it is the only field in a tab, whose label already names it. Pass field options to change it, for example commentsField({ label: 'Discussion' }). Both fields show on the edit page and in the record panel.
The list shows the latest 50 comments, oldest first. Each shows the author’s picture and name, when it was posted (“Just now”, “6 minutes ago”, then a date after a day), and “(edited)” when it was changed. Hovering your own comment shows a ··· menu to edit it in place or delete it. Typing in the box never marks the record’s form as changed: Comment saves through the comments API.
Names and pictures
Comments, the@ menu and mentions name people the way the rest of the admin does:
- Name: the users collection’s
admin.useAsTitle, then their email. SetuseAsTitle: 'name'on a users collection with a name field to show names rather than emails. - Picture: the app’s
admin.avatar, with no extra setting.'gravatar'(the default) shows each person’s Gravatar, or their initials when they have none.'default'shows initials.- A custom
{ Component }renders on comment rows with the person asuserand the size in pixels assize. Read the person fromuser, not the signed-in user. The@menu shows initials for it, since its results load in the browser.
depth, so a renamed person reads correctly in old comments.
Choosing the editor
Comments use the same order as any rich text field: the app’seditor, then the plugin’s editor, then the collection’s.
MentionFeature() is added when it’s missing, because mentions record who a comment is for. commentFeatures() returns the compact set: bold, italic, strikethrough, inline code, links, lists and mentions.
Each different editor gets its own hidden rich text field on the comments collection, so a comment is validated, and its uploads and links are populated, with exactly the features of the editor it was written in. You never name these fields: the API reads and writes a comment’s rich text as body. A collection can’t hold two comments fields with different editors.
The comments collection
Access
FrogBot adds no tenant rules. The defaults:- Read: signed in, and only comments on records the user may read, checked with each collection’s own read access.
- Create: signed in, on a collection with comments, on a record the user may read.
- Update and delete: the comment’s author.
overrides.access.
Notifications
With the notifications plugin installed, a comment notifies each user it newly mentions, once. Editing a comment notifies only the users the edit adds, and a user who can’t read the record isn’t notified. Without it, mentions are still recorded inmentions.
Custom views
The pieces the field uses are exported for custom views and dashboards:RecordComments loads a record’s comments with the signed-in user’s access and renders the list and box, or nothing when the user can’t read the record. The client parts are in @frogbotai/plugin-comments/client: Comments (list and box, reloading after changes), CommentList, CommentBox, CommentEditor (the rich text box with its own value) and formatWhen. UserAvatar from @frogbotai/ui draws a person’s Gravatar or initials anywhere else.