<%= form_for resource, html: { class: 'resource' } do |f| %>
  <% if local_assigns[:parent].present? %>
    <p>
      <label for="parent-name">Parent:</label>
      <%= text_field_tag 'parent-name', "#{parent.title} (#{parent.base_path})", disabled: true %>
      <%= f.hidden_field :parent_id, value: parent.id %>
    </p>
  <% end %>

  <%= f.text_field :slug %>
  <%= f.text_field :title %>
  <%= f.text_field :description %>

  <div class="form-actions">
    <button type="submit">
      <%= resource.new_record? ? 'Create' : 'Save' %>
    </button>
  </div>
<% end %>

<%= form_for resource, html: { class: 'resource' } do |f| %>
  <% if local_assigns[:parent].present? %>
    <p>
      <label for="parent-name">Parent:</label>
      <%= text_field_tag 'parent-name', "#{parent.title} (#{parent.base_path})", disabled: true %>
      <%= f.hidden_field :parent_id, value: parent.id %>
    </p>
  <% end %>

  <%= f.text_field :slug %>
  <%= f.text_field :title %>
  <%= f.text_field :description %>

  <% if f.object.published? && f.object.dirty? %>
    <div class="callout callout-warning">
      <span class="callout-title">Warning</span>
      This <%= tag_type_label %> has unpublished changes to the curated lists.  Saving will publish these changes.
    </div>
  <% end %>

  <div class="form-actions">
    <button type="submit">
      <%= resource.new_record? ? 'Create' : 'Save' %>
    </button>
  </div>
<% end %>

Add warning to tag editing page for dirty tags
Add warning to tag editing page for dirty tags

When changes to a published tag's properties are saved, the changes have
to be sent to the publishing-api.  This process will also send all
curated lists, including those that are pending.  This PR therefore adds
a warning to the edit form indicating that this is the case.

The process has to work this way because we have no workflow around the
curating of topics, and therefore don't have the previously published
curated lists to be able to re-send to publishing-api.
