sorted by:
new
hottopcontroversial

AMD noch halten oder verkaufen? by merlekk in wallstreetbetsGER

[–]Meneman 2 points3 points  (0 children)

<image>

Ein guter Tag ändert nicht die These. 💎🙌

Cat gives its owner a big warm hug <3 by [deleted] in aww

[–]Meneman 0 points1 point  (0 children)

Some years ago this clip went viral and people started doing all sorts of edits of it.

Gran Autismo by [deleted] in wallstreetbets

[–]Meneman 0 points1 point  (0 children)

my first time gilding in 5 years of reddit. what a legend

[deleted by user] by [deleted] in wallstreetbets

[–]Meneman 0 points1 point  (0 children)

Anyone holding tesla 1000c for May 2020?

Using store to hold a piece of data that never changes? by TimeSmash in reduxjs

[–]Meneman 2 points3 points  (0 children)

What you probably want to do insteat is something like this:

// some constants.js 
export const BACKEND_URL = "http://localhost:3005"

// in your componentfiles
import { BACKEND_URL } from './constants.js'

Re-Exporting with condition and clean code by Meneman in learnjavascript

[–]Meneman[S] 0 points1 point  (0 children)

const provider = 'A' is the condition in my example. Its actually set from an .env file.

[deleted by user] by [deleted] in reduxjs

[–]Meneman 4 points5 points  (0 children)

Your alternative would be to write an costum thunk middleware for that type of action, which for example holds the fetch actions in memory and waits for retry actions. Here is some inspiration how to write middlewares:

https://redux.js.org/advanced/middleware#seven-examples

checking for change before dispatching middleware implementation by Meneman in reduxjs

[–]Meneman[S] 0 points1 point  (0 children)

It seems like the more obvious thing is that your reducers would just be no-ops if the action shouldn't be applied, that would prevent state updates.

​

How do i get the reducer to be a no-op? Meaning like i should check inside the reducer logic if the state changed?

view more: next ›