We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In the following code, we are not adding label options for exhibit tags.
spotlight/app/models/spotlight/blacklight_configuration.rb
Lines 315 to 327 in ebed5d6
It could be that the lack of labels is not a bug as folks could add to the catalog controller the show and facet fields.
Would the following change be appropriate?
def add_exhibit_tags_fields(config) # rubocop:disable Style/GuardClause unless config.show_fields.include? :exhibit_tags config.add_show_field( :exhibit_tags, field: config.document_model.solr_field_for_tagger(exhibit), link_to_facet: true, separator_options: { words_connector: nil, two_words_connector: nil, last_word_connector: nil }, label: I18n.t('spotlight.search.fields.facet.exhibit_tags') ) end unless config.facet_fields.include? :exhibit_tags config.add_facet_field( :exhibit_tags, field: config.document_model.solr_field_for_tagger(exhibit), limit: true, label: I18n.t('spotlight.search.fields.facet.exhibit_tags') ) end # rubocop:enable Style/GuardClause end
The text was updated successfully, but these errors were encountered:
Adding label to auto-injected exhibit_tags field
acea401
This builds on https://github.com/harvard-lts/CURIOSity/issues/188 Closes projectblacklight#2842
Successfully merging a pull request may close this issue.
In the following code, we are not adding label options for exhibit tags.
spotlight/app/models/spotlight/blacklight_configuration.rb
Lines 315 to 327 in ebed5d6
It could be that the lack of labels is not a bug as folks could add to the catalog controller the show and facet fields.
Would the following change be appropriate?
The text was updated successfully, but these errors were encountered: