This MR provides…
- Transfer intranet text styling specification info to key modal.
Note: Keys button is placed next to increase/decrease buttons inside Text Panel, since there is an existing issue related to responsive heights.
Note: Closing this MR to fix panels height bug first and open a new one with requested changes.
Does the result of the MR comply to our "definition of done"?
Unit tests passed
Acceptance criteria met
Functional tests passed
Non-Functional requirements met
Product Owner accepts the User Story
I updated the README (if applicable)
I provided my functions with appropriate documentation
I adjusted other parts of the documentation (if applicable)
Are we able to test this new feature?
Yes, everything can be done via unit tests.
Yes, you can test by following these steps: A new button is created next to increase and decrease button inside text panel. When you click on it, a modal is opened and you can view the labels of related text styles explained. since most of the keys in text panel are handled from annotation panel, the display of keys button appears only when there are any specific keys to display. ex: Karshuni Collection: https://ahikar-dev.sub.uni-goettingen.de/api/textapi/ahikar/arabic-karshuni/collection.json Borg. Arab. 201 - sheet 199a, 200a or. 1292. The Arabic Text in Leiden. - sheet 194. Cod. Sach. 339 - Sheet p.1, p.2, p.3, p.4, p.5...
MSS_611 - sheet 1v
No, it is not possible.
I added a statement to the CHANGELOG.
Add all related issues and especially those to be closed.