Draft: fix/#356: Brackets in link text and lists of links cause an error
Bug fix
Summary
- Show the full link text which is in the brackets.
- List of all the links that can be available for a Metadata value.
To test list of links:
- please pull the branch
fix/#356-url-text
in local and navigate tourls.vue
component. - Comment out the lines from 37 - 42 and add the following sample value below:
data() { return { content: '30. März 1822. Hegel an Kultusministerium (https://dev.gfl.sub.uni-goettingen.de/id/Z_1822-03-30_k); 3. April 1822. Von Henning an Altenstein (https://dev.gfl.sub.uni-goettingen.de/id/Z_1822-04-03_k); 24. Juni 1820. Hardenberg an Altenstein (Ausfertigung) (https://dev.gfl.sub.uni-goettingen.de/id/Z_1820-06-24_k); 8. Juli 1820. Altenstein an Hardenberg (Konzept) (https://dev.gfl.sub.uni-goettingen.de/id/Z_1820-07-08_k); 22. Juli 1820. Hardenberg an Altenstein (Ausfertigung) (https://dev.gfl.sub.uni-goettingen.de/id/Z_1820-07-22_k)', }; },
- This is a sample value of Metadata from GFL and once we run the app, navigate to Metadata tab and we can notice the links are displayed as expected.
Sample screenshot:
Does the result of the MR comply to our "definition of done"?
-
Unit tests passed -
Code reviewed -
Acceptance criteria met -
Functional tests passed -
Non-Functional requirements met -
Product Owner accepts the User Story
Related
Closes
Changelog
-
I added a statement to the CHANGELOG.
Documentation
-
I updated the README (if applicable) -
I provided my functions with appropriate documentation
Merge request reports
Activity
requested review from @paul.pestov, @mgoebel, @kvoigt1, @rmraschkowski, @asajedi, and @nwindis
assigned to @manikanth.dindigala
- Resolved by Manikanth Dindigala
I get a
Access to fetch at 'https://ahikar.sub.uni-goettingen.de/api/textapi/ahikar/syriac/collection.json' from origin 'http://0.0.0.0:8080' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.
Any idea what causes it and/or how it can be fixed?
(VPN active)
Edited by Nils Windisch
- Resolved by Manikanth Dindigala
Could you please elaborate on the "as expected" part of the ticket description, thank you.
removed review request for @nwindis