Links acting like buttons have a few disadvantages.
First, screen readers will announce them as "links". Screen reader users
usually associate links with "things that get you somewhere" and buttons
with "things that perform an action". So when something like "Delete,
link" is announced, they'll probably think this is a link which will
take them to another page where they can delete a record.
Furthermore, the URL of the link for the "destroy" action might be the
same as the URL for the "show" action (only one is accessed with a
DELETE request and the other one with a GET request). That means screen
readers could announce the link like "Delete, visited link", which is
very confusing.
They also won't work when opening links in a new tab, since opening
links in a new tab always results in a GET request to the URL the link
points to.
Finally, submit buttons work without JavaScript enabled, so they'll work
even if the JavaScript in the page hasn't loaded (for whatever reason).
For all these reasons (and probably many more), using a button to send
forms is IMHO superior to using links.
There's one disadvantage, though. Using `button_to` we create a <form>
tag, which means we'll generate invalid HTML if the table is inside
another form. If we run into this issue, we need to use `button_tag`
with a `form` attribute and then generate a form somewhere else inside
the HTML (with `content_for`).
Note we're using `button_to` with a block so it generates a <button>
tag. Using it in a different way the text would result in an <input />
tag, and input elements can't have pseudocontent added via CSS.
The following code could be a starting point to use the `button_tag`
with a `form` attribute. One advantage of this approach is screen
readers wouldn't announce "leaving form" while navigating through these
buttons. However, it doesn't work in Internet Explorer.
```
ERB:
<% content_for(:hidden_content, form_tag(path, form_options) {}) %>
<%= button_tag text, button_options %>
Ruby:
def form_id
path.gsub("/", "_")
end
def form_options
{ id: form_id, method: options[:method] }
end
def button_options
html_options.except(:method).merge(form: form_id)
end
Layout:
<%= content_for :hidden_content %> # Right before the `</body>`
```
115 lines
3.4 KiB
Ruby
115 lines
3.4 KiB
Ruby
require "rails_helper"
|
|
|
|
describe "Valuator groups", :admin do
|
|
scenario "Index" do
|
|
group1 = create(:valuator_group)
|
|
group2 = create(:valuator_group)
|
|
3.times { create(:valuator, valuator_group: group1) }
|
|
|
|
visit admin_valuator_groups_path
|
|
|
|
within("#valuator_group_#{group1.id}") do
|
|
expect(page).to have_content group1.name
|
|
expect(page).to have_content 3
|
|
end
|
|
|
|
within("#valuator_group_#{group2.id}") do
|
|
expect(page).to have_content group2.name
|
|
expect(page).to have_content 0
|
|
end
|
|
end
|
|
|
|
scenario "Show" do
|
|
group = create(:valuator_group)
|
|
valuator1 = create(:valuator, valuator_group: group)
|
|
valuator2 = create(:valuator, valuator_group: group)
|
|
valuator3 = create(:valuator, valuator_group: nil)
|
|
|
|
visit admin_valuator_group_path(group)
|
|
|
|
expect(page).to have_content group.name
|
|
|
|
within("#valuators") do
|
|
expect(page).to have_link(valuator1.email, href: admin_valuator_path(valuator1))
|
|
expect(page).to have_link(valuator2.email, href: admin_valuator_path(valuator2))
|
|
expect(page).not_to have_link(valuator3.email)
|
|
end
|
|
end
|
|
|
|
scenario "Create" do
|
|
visit admin_valuators_path
|
|
|
|
click_link "Valuator Groups"
|
|
click_link "Create valuators group"
|
|
|
|
fill_in "valuator_group_name", with: "Health"
|
|
click_button "Create valuators group"
|
|
|
|
expect(page).to have_content "Valuator group created successfully"
|
|
expect(page).to have_content "There is 1 valuator group"
|
|
expect(page).to have_content "Health"
|
|
end
|
|
|
|
scenario "Update" do
|
|
create(:valuator_group, name: "Health")
|
|
|
|
visit admin_valuator_groups_path
|
|
click_link "Edit"
|
|
|
|
fill_in "valuator_group_name", with: "Health and Sports"
|
|
click_button "Save valuators group"
|
|
|
|
expect(page).to have_content "Valuator group updated successfully"
|
|
expect(page).to have_content "Health and Sports"
|
|
end
|
|
|
|
scenario "Delete" do
|
|
create(:valuator_group)
|
|
|
|
visit admin_valuator_groups_path
|
|
accept_confirm { click_button "Delete" }
|
|
|
|
expect(page).to have_content "Valuator group deleted successfully"
|
|
expect(page).to have_content "There are no valuator groups"
|
|
end
|
|
|
|
context "Assign valuators to groups" do
|
|
let(:valuator) { create(:valuator) }
|
|
|
|
scenario "Add a valuator to a group" do
|
|
create(:valuator_group, name: "Health")
|
|
|
|
visit edit_admin_valuator_path(valuator)
|
|
|
|
select "Health", from: "valuator_valuator_group_id"
|
|
click_button "Update Valuator"
|
|
|
|
expect(page).to have_content "Valuator updated successfully"
|
|
expect(page).to have_content "Health"
|
|
end
|
|
|
|
scenario "Update a valuator's group" do
|
|
valuator.update!(valuator_group: create(:valuator_group, name: "Economy"))
|
|
create(:valuator_group, name: "Health")
|
|
|
|
visit edit_admin_valuator_path(valuator)
|
|
select "Economy", from: "valuator_valuator_group_id"
|
|
click_button "Update Valuator"
|
|
|
|
expect(page).to have_content "Valuator updated successfully"
|
|
expect(page).to have_content "Economy"
|
|
end
|
|
|
|
scenario "Remove a valuator from a group" do
|
|
valuator.update!(valuator_group: create(:valuator_group, name: "Health"))
|
|
|
|
visit edit_admin_valuator_path(valuator)
|
|
select "", from: "valuator_valuator_group_id"
|
|
click_button "Update Valuator"
|
|
|
|
expect(page).to have_content "Valuator updated successfully"
|
|
expect(page).not_to have_content "Health"
|
|
end
|
|
end
|
|
end
|