app-monorepo
app-monorepo copied to clipboard
feat: support mutiple lines in Toast Message
PR Summary
-
Updated Dependencies Two additional dependencies were included in the project files for enhanced functionality. The 'mobile/package.json' got a new dependency '@backpackapp-io/react-native-toast' and another one, 'sonner' was added to 'package.json'.
-
Refactoring Toast Component The Toast component files underwent significant changes. A specific file 'ShowToaster.tsx' was renamed to 'ShowCustom.tsx', and its export name was changed correspondingly.
-
Deletion and Addition of Files The file 'Toast.native.tsx' was completely removed from the project structure. In contrast, a new file 'Toaster.native.tsx' was inserted to provide updated features.
-
Updated Component Import Statements The contents of 'Toaster.tsx' and 'index.tsx' were altered. The updated import statement now pulls 'Toaster' from the newly included 'sonner' library, and certain props were introduced to the 'Toaster' component. In addition, 'index.tsx' had its import statements changed, and it now reexports the 'useToaster' hook and 'IShowToasterProps' type from 'ShowCustom.tsx'.
-
Added New Files Three new files named 'showMessage.native.tsx','showMessage.tsx', and 'type.ts' were added under the Toast actions.
-
Updated React Provider Structure The file 'index.tsx' under 'kit/src/provider' was amended to nest the 'ThemeProvider' component within the 'GestureHandlerRootView' component.
-
Developer Pages Gallery Modification Changes were also incorporated into 'Toast.tsx' in the 'Developer/pages/Gallery/Components/stories', where new buttons rendering different toast messages and durations were added.
-
Introduced New Constant A fresh constant 'TOAST_Z_INDEX' was added to 'overlayUtils.ts'.
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: npm/@babel/[email protected], npm/@babel/[email protected], npm/@protobufjs/[email protected], npm/@sindresorhus/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected]
👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎
This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.
Ignoring: npm/[email protected]
Next steps
Take a deeper look at the dependency
Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.
Remove the package
If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.
Mark a package as acceptable risk
To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all
@SocketSecurity ignore npm/[email protected] @SocketSecurity ignore npm/[email protected] @SocketSecurity ignore npm/[email protected] @SocketSecurity ignore npm/[email protected]
@SocketSecurity ignore npm/[email protected]