Prompt without class stripping?

[randohinn]

Is there a way to not have lexxy prompts strip classes from the editor? I would've thought insert-editable-text would be for that, but nope...

  <%= f.rich_text_area :body do %>
    <lexxy-prompt trigger="@"  insert-editable-text>
      <lexxy-prompt-item search="link" src >
        <template type="menu">Konkursikeskkonna link</template>
        <template type="editor">
          <p class="btn">
              <%= link_to "Konkursikeskkond", root_url %>
          </p>
        </template>
      </lexxy-prompt-item>
    </lexxy-prompt>
  <% end %>

[randohinn]

@jorgemanrubia any ideas on what I might do here?

[jorgemanrubia]

The class stripping isn't a sanitization issue — it's how insert-editable-text works. That option converts the template's HTML into Lexical's editable document model, and Lexical nodes only carry the attributes they model (a <p> becomes a paragraph node that knows about format and indentation, a link keeps its href, etc.). Arbitrary attributes like class have nowhere to live, and the HTML you get back is regenerated from that model. So insert-editable-text is meant for inserting plain editable content, not for preserving custom markup.

For a self-contained styled snippet like yours, use the default attachment insertion instead — just drop insert-editable-text and give the prompt a name:

<%= f.rich_text_area :body do %>
  <lexxy-prompt trigger="@" name="link">
    <lexxy-prompt-item search="link">
      <template type="menu">Konkursikeskkonna link</template>
      <template type="editor">
        <p class="btn">
          <%= link_to "Konkursikeskkond", root_url %>
        </p>
      </template>
    </lexxy-prompt-item>
  </lexxy-prompt>
<% end %>

This inserts the template as an Action Text content attachment, which stores your HTML verbatim — class="btn" included — and survives saving and rendering. The trade-off is that the inserted content behaves as a single non-editable unit in the editor rather than editable text, but for a styled link block that's usually what you want anyway. Note it renders wrapped in a <figure class="attachment attachment--content">, so you may want to account for that in your CSS.