fix current logic error in displaying/hiding feature/unfeature buttons #3776
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #3169
The current implementation of showing/hiding feature/unfeature buttons seems to be incorrect.
e.g. for feature button:
<%= link_to "Feature", hyrax.featured_work_path(presenter, format: :json),
data: { behavior: 'feature' },
class: presenter.display_unfeature_link? ? 'btn btn-default collapse' : 'btn btn-default' %>
It says, "if display_unfeature_link returns true, then hide feature button, OTHERWISE, show feature button". While display_unfeature_link returns false, it doesn't necessarily mean feature button needs to be shown. For example, when 5 works have been featured already, both feature/unfeature buttons should be hidden for new objects. Therefore, to make it simple and working:
<%= link_to t('.feature'), hyrax.featured_work_path(presenter, format: :json),
data: { behavior: 'feature' },
class: presenter.display_feature_link? ? 'btn btn-default' : 'btn btn-default collapse' %>
@samvera/hyrax-code-reviewers