Skip to content
This repository has been archived by the owner on Jun 20, 2023. It is now read-only.

Change FAQ links reg. DCC ticketing (COMMUNITY) #4448

Closed
wants to merge 2 commits into from
Closed

Change FAQ links reg. DCC ticketing (COMMUNITY) #4448

wants to merge 2 commits into from

Conversation

Ein-Tim
Copy link
Contributor

@Ein-Tim Ein-Tim commented Apr 11, 2022

Description

This PR changes a FAQ link reg. the DCC ticketing feature, as the linked FAQ entries are about to be removed (corona-warn-app/cwa-website#2734).

Link to Jira

No link yet.

Screenshots

Not possible, no UI changes.

This commit changes a FAQ link reg. the DCC ticketing feature, as the linked FAQ entries are removed.
@Ein-Tim Ein-Tim requested review from a team April 11, 2022 15:32
@Ein-Tim
Copy link
Contributor Author

Ein-Tim commented Apr 11, 2022

Am I missing something or is there no Localizable.links.strings file for the Ukrainian language?

@Ein-Tim Ein-Tim changed the title Change FAQ links reg. DCC ticketing Change FAQ links reg. DCC ticketing (COMMUNITY) Apr 12, 2022
@Ein-Tim
Copy link
Contributor Author

Ein-Tim commented Apr 12, 2022

@marcussc Could you please approve the workflows to run? I guess because of the transition to GitHub Actions, I'm a "first time contributor" :D

@dsarkar
Copy link
Member

dsarkar commented Apr 12, 2022

@Ein-Tim This has been discussed internally: With your PR corona-warn-app/cwa-website#2734 including the redirects of the corresponding FAQ articles on the webpage there is no need for this change in the app. Anyway, as long there is no validation service provided, app users will never see these FAQ links in the app.

@Ein-Tim
Copy link
Contributor Author

Ein-Tim commented Apr 12, 2022

@dsarkar Agreed! Closing.

@Ein-Tim Ein-Tim closed this Apr 12, 2022
@Ein-Tim Ein-Tim deleted the fix/FAQ-links branch April 12, 2022 13:07
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants