Is your feature request related to a problem? Please describe.
Currently, Font Awesome icon customization is inconsistent. Some icons can be easily customized via config.yml, while others are hardcoded directly into HTML/TS files (requiring a full UI rebuild to change)
Describe the solution you'd like
Make all Font Awesome icons configurable in the same way. Ideally in a way that does not require modifying suorce code or recompiling the frontend.
Describe alternatives or workarounds you've considered
The current workaround is to override or edit templates to change icons (and checking if an icon is already exposed in the configuration).
Additional information
Few examples:
|
icons: |
|
metadata: |
|
# NOTE: example of configuration |
|
# # NOTE: metadata name |
|
# - name: dc.author |
|
# # NOTE: fontawesome (v6.x) icon classes and bootstrap utility classes can be used |
|
# style: fas fa-user |
|
- name: dc.author |
|
style: fas fa-user |
|
authority: |
|
confidence: |
|
# NOTE: example of configuration |
|
# # NOTE: confidence value |
|
# - value: 600 |
|
# # NOTE: fontawesome (v6.x) icon classes and bootstrap utility classes can be used |
|
# style: text-success |
|
# icon: fa-circle-check |
|
# # NOTE: the class configured in property style is used by default, the icon property could be used in component |
|
# configured to use a 'icon mode' display (mainly in edit-item page) |
|
- value: 600 |
|
style: text-success |
|
icon: fa-circle-check |
|
- value: 500 |
|
style: text-info |
|
icon: fa-gear |
|
modalRef.componentInstance.confirmIcon = 'fas fa-trash'; |
|
toggleIcon: 'far fa-calendar-alt', |
Is your feature request related to a problem? Please describe.
Currently, Font Awesome icon customization is inconsistent. Some icons can be easily customized via
config.yml, while others are hardcoded directly into HTML/TS files (requiring a full UI rebuild to change)Describe the solution you'd like
Make all Font Awesome icons configurable in the same way. Ideally in a way that does not require modifying suorce code or recompiling the frontend.
Describe alternatives or workarounds you've considered
The current workaround is to override or edit templates to change icons (and checking if an icon is already exposed in the configuration).
Additional information
Few examples:
dspace-angular/config/config.example.yml
Lines 199 to 207 in a52ba24
dspace-angular/config/config.example.yml
Lines 215 to 230 in a52ba24
dspace-angular/src/app/submission/edit/pending-changes/pending-changes.guard.ts
Line 62 in a52ba24
dspace-angular/src/app/shared/menu/providers/new.menu.ts
Line 49 in a52ba24
dspace-angular/src/app/submission/sections/upload/file/edit/section-upload-file-edit.model.ts
Line 81 in a52ba24