Add page titles (affects browser Tab, History, etc.)
## Issue
- While changing the "Back" behavior in the Settings Page PR, it was a pain to troubleshoot when the entire history list is listed as "odysee.com".
- If you have multiple tabs open, it's hard to know which is which for non-claim and non-channel pages.
## Approach
Initially, I thought of overriding the document's title through the `<Page>` component, since the titles are usually defined there. However, given that the router is already doing the overriding, I think it's best to do the same thing all in one place.
Downside: it might get missed when a new page is added.
## Unknown
- Not sure if are rules for titles. There seems to be a mix of sites -- some have specific titles per page, most just use the site title for each page.
- I think the `return` statement in the `useEffect` is unnecessary, since it'll just be setting to the same value now during the cleanup stage. (??)
2021-08-25 16:26:53 +02:00
|
|
|
// Customer-facing title for a page.
|
|
|
|
|
//
|
|
|
|
|
// Primarily used for the browser tab and history title.
|
2021-09-30 08:36:27 +02:00
|
|
|
// Ensure new strings are added to 'app-string.json' for localization.
|
Add page titles (affects browser Tab, History, etc.)
## Issue
- While changing the "Back" behavior in the Settings Page PR, it was a pain to troubleshoot when the entire history list is listed as "odysee.com".
- If you have multiple tabs open, it's hard to know which is which for non-claim and non-channel pages.
## Approach
Initially, I thought of overriding the document's title through the `<Page>` component, since the titles are usually defined there. However, given that the router is already doing the overriding, I think it's best to do the same thing all in one place.
Downside: it might get missed when a new page is added.
## Unknown
- Not sure if are rules for titles. There seems to be a mix of sites -- some have specific titles per page, most just use the site title for each page.
- I think the `return` statement in the `useEffect` is unnecessary, since it'll just be setting to the same value now during the cleanup stage. (??)
2021-08-25 16:26:53 +02:00
|
|
|
|
|
|
|
|
import * as PAGES from 'constants/pages';
|
|
|
|
|
|
|
|
|
|
export const PAGE_TITLE = {
|
|
|
|
|
// --- Categories ---
|
2022-04-29 09:57:23 +02:00
|
|
|
// Dynamically populated in 'window.CATEGORY_PAGE_TITLE'.
|
Add page titles (affects browser Tab, History, etc.)
## Issue
- While changing the "Back" behavior in the Settings Page PR, it was a pain to troubleshoot when the entire history list is listed as "odysee.com".
- If you have multiple tabs open, it's hard to know which is which for non-claim and non-channel pages.
## Approach
Initially, I thought of overriding the document's title through the `<Page>` component, since the titles are usually defined there. However, given that the router is already doing the overriding, I think it's best to do the same thing all in one place.
Downside: it might get missed when a new page is added.
## Unknown
- Not sure if are rules for titles. There seems to be a mix of sites -- some have specific titles per page, most just use the site title for each page.
- I think the `return` statement in the `useEffect` is unnecessary, since it'll just be setting to the same value now during the cleanup stage. (??)
2021-08-25 16:26:53 +02:00
|
|
|
|
|
|
|
|
// --- Everything else in alphabetical order ---
|
|
|
|
|
[PAGES.BUY]: 'Buy or Swap',
|
|
|
|
|
[PAGES.CHANNELS]: 'Your channels',
|
|
|
|
|
[PAGES.CHANNELS_FOLLOWING]: 'Following',
|
|
|
|
|
[PAGES.CHANNELS_FOLLOWING_DISCOVER]: 'Discover Channels',
|
|
|
|
|
[PAGES.CHANNEL_NEW]: 'Create a channel',
|
|
|
|
|
[PAGES.CHECKOUT]: 'Checkout',
|
|
|
|
|
[PAGES.CODE_2257]: '2257',
|
|
|
|
|
[PAGES.CREATOR_DASHBOARD]: 'Creator Analytics',
|
2022-03-17 10:00:03 +01:00
|
|
|
[PAGES.FYP]: 'Recommended Videos (Alpha)',
|
Add page titles (affects browser Tab, History, etc.)
## Issue
- While changing the "Back" behavior in the Settings Page PR, it was a pain to troubleshoot when the entire history list is listed as "odysee.com".
- If you have multiple tabs open, it's hard to know which is which for non-claim and non-channel pages.
## Approach
Initially, I thought of overriding the document's title through the `<Page>` component, since the titles are usually defined there. However, given that the router is already doing the overriding, I think it's best to do the same thing all in one place.
Downside: it might get missed when a new page is added.
## Unknown
- Not sure if are rules for titles. There seems to be a mix of sites -- some have specific titles per page, most just use the site title for each page.
- I think the `return` statement in the `useEffect` is unnecessary, since it'll just be setting to the same value now during the cleanup stage. (??)
2021-08-25 16:26:53 +02:00
|
|
|
[PAGES.HELP]: 'Help',
|
|
|
|
|
[PAGES.INVITE]: 'Invite',
|
2022-04-07 18:10:39 +02:00
|
|
|
[PAGES.LIBRARY]: 'Purchases',
|
Playlists v2: Refactors, touch ups + Queue Mode (#1604)
* Playlists v2
* Style pass
* Change playlist items arrange icon
* Playlist card body open by default
* Refactor collectionEdit components
* Paginate & Refactor bid field
* Collection page changes
* Add Thumbnail optional
* Replace extra info for description on collection page
* Playlist card right below video on medium screen
* Allow editing private collections
* Add edit option to menus
* Allow deleting a public playlist but keeping a private version
* Add queue to Save menu, remove edit option from Builtin pages, show queue on playlists page
* Fix scroll to recent persisting on medium screen
* Fix adding to queue from menu
* Fixes for delete
* PublishList: delay mounting Items tab to prevent lock-up (#1783)
For a large list, the playlist publish form is unusable (super-slow typing) due to the entire list being mounted despite the tab is not active.
The full solution is still to paginate it, but for now, don't mount the tab until it is selected. Add a spinner to indicate something is loading. It's not prefect, but it's throwaway code anyway. At least we can fill in the fields properly now.
* Batch-resolve private collections (#1782)
* makeSelectClaimForClaimId --> selectClaimForClaimId
Move away from the problematic `makeSelect*`, especially in large loops.
* Batch-resolve private collections
1758
This alleviates the lock-up that is caused by large number of invidual resolves. There will still be some minor stutter due to the large DOM that React needs to handle -- that is logged in 1758 and will be handled separately.
At least the stutter is short (1-2s) and the app is still usable.
Private list items are being resolve individually, super slow if the list is large (>100). Published lists doesn't have this issue.
doFetchItemsInCollections contains most of the useful logic, but it isn't called for private/built-in lists because it's not an actual claim.
Tweaked doFetchItemsInCollections to handle private (UUID-based) collections.
* Use persisted state for floating player playlist card body
- I find it annoying being open everytime
* Fix removing edits from published playlist
* Fix scroll on mobile
* Allow going editing items from toast
* Fix ClaimShareButton
* Prevent edit/publish of builtin
* Fix async inside forEach
* Fix sync on queue edit
* Fix autoplayCountdown replay
* Fix deleting an item scrolling the playlist
* CreatedAt fixes
* Remove repost for now
* Anon publish fixes
* Fix mature case on floating
Co-authored-by: infinite-persistence <64950861+infinite-persistence@users.noreply.github.com>
2022-07-13 15:59:59 +02:00
|
|
|
[PAGES.LISTS]: 'Playlists',
|
|
|
|
|
[PAGES.PLAYLISTS]: 'Playlists',
|
Add page titles (affects browser Tab, History, etc.)
## Issue
- While changing the "Back" behavior in the Settings Page PR, it was a pain to troubleshoot when the entire history list is listed as "odysee.com".
- If you have multiple tabs open, it's hard to know which is which for non-claim and non-channel pages.
## Approach
Initially, I thought of overriding the document's title through the `<Page>` component, since the titles are usually defined there. However, given that the router is already doing the overriding, I think it's best to do the same thing all in one place.
Downside: it might get missed when a new page is added.
## Unknown
- Not sure if are rules for titles. There seems to be a mix of sites -- some have specific titles per page, most just use the site title for each page.
- I think the `return` statement in the `useEffect` is unnecessary, since it'll just be setting to the same value now during the cleanup stage. (??)
2021-08-25 16:26:53 +02:00
|
|
|
[PAGES.LIVESTREAM]: 'Go Live on Odysee',
|
|
|
|
|
[PAGES.LIVESTREAM_CURRENT]: 'Live (Experimental)',
|
|
|
|
|
[PAGES.NOTIFICATIONS]: 'Notifications',
|
2022-03-17 10:00:03 +01:00
|
|
|
[PAGES.ODYSEE_MEMBERSHIP]: 'Odysee Premium',
|
2022-07-11 16:12:37 +02:00
|
|
|
[PAGES.POST]: 'Post an Article on Odysee',
|
2022-03-17 10:00:03 +01:00
|
|
|
[PAGES.PRIVACY_POLICY]: 'Privacy Policy',
|
Add page titles (affects browser Tab, History, etc.)
## Issue
- While changing the "Back" behavior in the Settings Page PR, it was a pain to troubleshoot when the entire history list is listed as "odysee.com".
- If you have multiple tabs open, it's hard to know which is which for non-claim and non-channel pages.
## Approach
Initially, I thought of overriding the document's title through the `<Page>` component, since the titles are usually defined there. However, given that the router is already doing the overriding, I think it's best to do the same thing all in one place.
Downside: it might get missed when a new page is added.
## Unknown
- Not sure if are rules for titles. There seems to be a mix of sites -- some have specific titles per page, most just use the site title for each page.
- I think the `return` statement in the `useEffect` is unnecessary, since it'll just be setting to the same value now during the cleanup stage. (??)
2021-08-25 16:26:53 +02:00
|
|
|
[PAGES.RECEIVE]: 'Your address',
|
|
|
|
|
[PAGES.REPORT]: 'Report an issue or request a feature',
|
|
|
|
|
[PAGES.REPORT_CONTENT]: 'Report content',
|
2022-05-03 13:57:39 +02:00
|
|
|
[PAGES.REPOST_NEW]: 'Repost',
|
Add page titles (affects browser Tab, History, etc.)
## Issue
- While changing the "Back" behavior in the Settings Page PR, it was a pain to troubleshoot when the entire history list is listed as "odysee.com".
- If you have multiple tabs open, it's hard to know which is which for non-claim and non-channel pages.
## Approach
Initially, I thought of overriding the document's title through the `<Page>` component, since the titles are usually defined there. However, given that the router is already doing the overriding, I think it's best to do the same thing all in one place.
Downside: it might get missed when a new page is added.
## Unknown
- Not sure if are rules for titles. There seems to be a mix of sites -- some have specific titles per page, most just use the site title for each page.
- I think the `return` statement in the `useEffect` is unnecessary, since it'll just be setting to the same value now during the cleanup stage. (??)
2021-08-25 16:26:53 +02:00
|
|
|
[PAGES.REWARDS]: 'Rewards',
|
|
|
|
|
[PAGES.REWARDS_VERIFY]: 'Verify to earn Credits',
|
|
|
|
|
[PAGES.SEARCH]: 'Search',
|
|
|
|
|
[PAGES.SEND]: 'Send Credits',
|
|
|
|
|
[PAGES.SETTINGS]: 'Settings',
|
2022-02-07 19:15:22 +01:00
|
|
|
[PAGES.SETTINGS_BLOCKED_MUTED]: 'Blocked and muted channels',
|
Add page titles (affects browser Tab, History, etc.)
## Issue
- While changing the "Back" behavior in the Settings Page PR, it was a pain to troubleshoot when the entire history list is listed as "odysee.com".
- If you have multiple tabs open, it's hard to know which is which for non-claim and non-channel pages.
## Approach
Initially, I thought of overriding the document's title through the `<Page>` component, since the titles are usually defined there. However, given that the router is already doing the overriding, I think it's best to do the same thing all in one place.
Downside: it might get missed when a new page is added.
## Unknown
- Not sure if are rules for titles. There seems to be a mix of sites -- some have specific titles per page, most just use the site title for each page.
- I think the `return` statement in the `useEffect` is unnecessary, since it'll just be setting to the same value now during the cleanup stage. (??)
2021-08-25 16:26:53 +02:00
|
|
|
[PAGES.SETTINGS_CREATOR]: 'Creator settings',
|
|
|
|
|
[PAGES.SETTINGS_NOTIFICATIONS]: 'Manage notifications',
|
2022-03-17 10:00:03 +01:00
|
|
|
[PAGES.SETTINGS_OWN_COMMENTS]: 'Your comments',
|
2021-09-30 08:36:27 +02:00
|
|
|
[PAGES.SETTINGS_STRIPE_ACCOUNT]: 'Bank Accounts',
|
|
|
|
|
[PAGES.SETTINGS_STRIPE_CARD]: 'Payment Methods',
|
Add page titles (affects browser Tab, History, etc.)
## Issue
- While changing the "Back" behavior in the Settings Page PR, it was a pain to troubleshoot when the entire history list is listed as "odysee.com".
- If you have multiple tabs open, it's hard to know which is which for non-claim and non-channel pages.
## Approach
Initially, I thought of overriding the document's title through the `<Page>` component, since the titles are usually defined there. However, given that the router is already doing the overriding, I think it's best to do the same thing all in one place.
Downside: it might get missed when a new page is added.
## Unknown
- Not sure if are rules for titles. There seems to be a mix of sites -- some have specific titles per page, most just use the site title for each page.
- I think the `return` statement in the `useEffect` is unnecessary, since it'll just be setting to the same value now during the cleanup stage. (??)
2021-08-25 16:26:53 +02:00
|
|
|
[PAGES.SETTINGS_UPDATE_PWD]: 'Update password',
|
|
|
|
|
[PAGES.SWAP]: 'Swap Credits',
|
|
|
|
|
[PAGES.TAGS_FOLLOWING]: 'Tags',
|
|
|
|
|
[PAGES.TAGS_FOLLOWING_MANAGE]: 'Manage tags',
|
2022-03-17 10:00:03 +01:00
|
|
|
[PAGES.TOS]: 'Terms of Service',
|
Add page titles (affects browser Tab, History, etc.)
## Issue
- While changing the "Back" behavior in the Settings Page PR, it was a pain to troubleshoot when the entire history list is listed as "odysee.com".
- If you have multiple tabs open, it's hard to know which is which for non-claim and non-channel pages.
## Approach
Initially, I thought of overriding the document's title through the `<Page>` component, since the titles are usually defined there. However, given that the router is already doing the overriding, I think it's best to do the same thing all in one place.
Downside: it might get missed when a new page is added.
## Unknown
- Not sure if are rules for titles. There seems to be a mix of sites -- some have specific titles per page, most just use the site title for each page.
- I think the `return` statement in the `useEffect` is unnecessary, since it'll just be setting to the same value now during the cleanup stage. (??)
2021-08-25 16:26:53 +02:00
|
|
|
[PAGES.UPLOADS]: 'Your uploads',
|
2022-07-11 16:12:37 +02:00
|
|
|
[PAGES.UPLOAD]: 'Upload a File to Odysee',
|
Add page titles (affects browser Tab, History, etc.)
## Issue
- While changing the "Back" behavior in the Settings Page PR, it was a pain to troubleshoot when the entire history list is listed as "odysee.com".
- If you have multiple tabs open, it's hard to know which is which for non-claim and non-channel pages.
## Approach
Initially, I thought of overriding the document's title through the `<Page>` component, since the titles are usually defined there. However, given that the router is already doing the overriding, I think it's best to do the same thing all in one place.
Downside: it might get missed when a new page is added.
## Unknown
- Not sure if are rules for titles. There seems to be a mix of sites -- some have specific titles per page, most just use the site title for each page.
- I think the `return` statement in the `useEffect` is unnecessary, since it'll just be setting to the same value now during the cleanup stage. (??)
2021-08-25 16:26:53 +02:00
|
|
|
[PAGES.WALLET]: 'Wallet',
|
2021-09-30 08:36:27 +02:00
|
|
|
[PAGES.YOUTUBE_SYNC]: 'YouTube Sync',
|
2022-03-17 10:00:03 +01:00
|
|
|
[PAGES.YOUTUBE_TOS]: 'YouTube Sync Terms of Service',
|
Add page titles (affects browser Tab, History, etc.)
## Issue
- While changing the "Back" behavior in the Settings Page PR, it was a pain to troubleshoot when the entire history list is listed as "odysee.com".
- If you have multiple tabs open, it's hard to know which is which for non-claim and non-channel pages.
## Approach
Initially, I thought of overriding the document's title through the `<Page>` component, since the titles are usually defined there. However, given that the router is already doing the overriding, I think it's best to do the same thing all in one place.
Downside: it might get missed when a new page is added.
## Unknown
- Not sure if are rules for titles. There seems to be a mix of sites -- some have specific titles per page, most just use the site title for each page.
- I think the `return` statement in the `useEffect` is unnecessary, since it'll just be setting to the same value now during the cleanup stage. (??)
2021-08-25 16:26:53 +02:00
|
|
|
};
|
