useNotification hook positioning
See original GitHub issueim having issue on using useNotification()
hook for position
const dispatch = useNotification();
const handleNotifications = (type, message, title) => {
dispatch({
type: type,
![IMG_0966](https://user-images.githubusercontent.com/31248378/161874610-33b4e26b-a0a2-42c5-adb5-7d4e5c2fcb55.JPG)
message: message,
title: title,
position: 'bottomL',
});
}
As you can see I’ve already added bottomL
but it still showing on top left + pushes all my components downwards. Im using nextjs by the way
Issue Analytics
- State:
- Created a year ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Building a reusable notification system with react hooks and ...
We use position: fixed; along with the top and right attributes to have the toast notification appear from the top-right corner of the...
Read more >React Notification Component - ReactJS Tutorial - YouTube
Learn how to make your own custom notification component in react js. By using the Context API and custom hooks we create to...
Read more >Web3 Dapp Developer Guide: React Hooks for Ethereum
To initialize the Notifications hook we will import `useNotifications()` hook from @web3-onboard/react and initialize in our App component ...
Read more >Mantine notifications system
To subscribe to notifications state use useNotifications hook, it returns object with the following properties: notifications – array of notifications that are ......
Read more >useNotificationCenter | React-Toastify - GitHub Pages
useNotificationCenter is a headless hook to build your notification center on top of react-toastify. In short, every time you call toast or any...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Great @ass77 , again, you can reach out next time you run into something similar.
Hey guys I managed to solved it by simply upgrade its version from
0.1.112
to0.1.113
. It seems to be working as expected now.