Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: move to react from preact #2173

Merged
merged 44 commits into from Sep 28, 2023
Merged

feat: move to react from preact #2173

merged 44 commits into from Sep 28, 2023

Conversation

capJavert
Copy link
Contributor

Changes

Describe what this PR does

Events

Did you introduce any new tracking events?
Don't forget to update the Analytics Taxonomy sheet

Log the new/changed events below:

Type event_name value
Change/New event name extra: { ... }

Please make sure existing components are not breaking/affected by this PR

Manual Testing

On those affected packages:

  • Have you done sanity checks in the webapp?
  • Have you done sanity checks in the extension?
  • Does this not break anything in companion?

Did you test the modified components media queries?

  • MobileL (420px)
  • Tablet (656px)
  • Laptop (1020px)

Did you test on actual mobile devices?

  • iOS (Chrome and Safari)
  • Android

WT-{number} #done

* feat: remove preact

* feat: remove alias configurations
feat: pass getContentScriptPermission instead of the hook which would trigger invalid hook call

feat: move origin as parameter for requestContentScripts to avoid requiring origin on places where

requestContentScripts is not used

feat: move useContentScriptStatus to shared
it was used for preact only
We used a dynamic render, but should have use our conditional render instead since it would simply render a empty fragment.

WT-1837 #done
Fixed useRef case, we manually defaulted to null and for this component it often doesn't get passed.
So using the "default" null is actually better and more stable.

WT-1849 #done
Add index key to tooltip on calendar heatmap render

WT-1854 #done
fixes timeout errors in CI on `waitFor`

ref WT-1834
* fix: notifications page build

* fix: portal unable to append to document

* refactor: seo needed outside
* refactor: nested anchor tags

* fix: optional prop
- the toast is triggered optimistically upon submission, so waiting for the mutation to finish executing might generate situations where the toast is already gone and the assertion would fail.

ref WT-1834
@rebelchris rebelchris requested a review from a team September 26, 2023 10:31
@capJavert capJavert enabled auto-merge (squash) September 28, 2023 09:16
@capJavert capJavert merged commit 111feb3 into main Sep 28, 2023
3 of 4 checks passed
@capJavert capJavert deleted the WT-1778-move-to-react branch September 28, 2023 09:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
5 participants