This PR return the build info which was lost when the app header was redesigned. Now the build info is accessible in 2 places: the Settings menu alongside other client info, and the footer on the landing page. Also, the build info is copied with the client info.
π Motivation and Context
closes #150
π§ͺ How Has This Been Tested?
Web and mobile
π· Screenshots (if appropriate)
π¦ Types of changes
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
β Checklist (copied from README)
[x] Squash your changes into a single clear and thoroughly descriptive commit, split changes into multiple commits only when it contributes to readability
[x] Reference the GitHub issue that you are contributing on in your commit title or body
[x] Sign your commits, as this is required by the automated GitHub PR checks
[x] Ensure that the changes adhere to the project code style and formatting rules by running npx eslint . and npx prettier --check ../ from the ./OwnTube.tv/ directory (without errors/warnings)
[x] Include links and illustrations in your pull request to make it easy to review
[x] Request a review by @mykhailodanilenko, @ar9708 and @mblomdahl
π Description
This PR return the build info which was lost when the app header was redesigned. Now the build info is accessible in 2 places: the Settings menu alongside other client info, and the footer on the landing page. Also, the build info is copied with the client info.
π Motivation and Context
closes #150
π§ͺ How Has This Been Tested?
Web and mobile
π· Screenshots (if appropriate)
π¦ Types of changes
β Checklist (copied from README)
npx eslint .
andnpx prettier --check ../
from the./OwnTube.tv/
directory (without errors/warnings)