You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 5, 2019. It is now read-only.
I found this new feature really interesting for chat feature developing as it also make use of ActiveStorage.
I tried to make it work on a API case but I founded the problem that the :content received at the controller is too specific to be generated by a frontend:
So, is there any plan to standardize it? or maybe introduce any option to install it like `rails action_text:install --api`` ?
I would be more than happy to lend a hand or even propose a pr, but first want to hear about the community due to being a couple of different ways to solve this
The text was updated successfully, but these errors were encountered:
APIs can accept attachment markup in canonicalized form (e.g. <action-text-attachment sgid="…"></action-text-attachment>) instead of the full Trix-compatible markup like you pasted above. This test may help illustrate. See Basecamp 3's API docs on Rich text too: https://github.com/basecamp/bc3-api/blob/master/sections/rich_text.md
APIs can accept attachment markup in canonicalized form (e.g. <action-text-attachment sgid="…"></action-text-attachment>) instead of the full Trix-compatible markup like you pasted above. This test may help illustrate. See Basecamp 3's API docs on Rich text too: https://github.com/basecamp/bc3-api/blob/master/sections/rich_text.md
This seems useful, so I would change my request to update README.md to provide this information with some example. Does that make sense?
I found this new feature really interesting for chat feature developing as it also make use of ActiveStorage.
I tried to make it work on a API case but I founded the problem that the
:content
received at the controller is too specific to be generated by a frontend:So, is there any plan to standardize it? or maybe introduce any option to install it like `rails action_text:install --api`` ?
I would be more than happy to lend a hand or even propose a pr, but first want to hear about the community due to being a couple of different ways to solve this
The text was updated successfully, but these errors were encountered: