MSW | A simple 16-bit CPU built in Logisim

The MSW documentation for request-url says:

I have MSW setup with React and Typescript, the code works in the browser, ie, it deletes the employee, but not in the test, the other tests are working fine. I'm stumped, there's probably something daft that I'm doing, any help would be greatly appreciated
github repo https://github.com/cherry15/cc2022react
handlers.ts

I'm using a wx.Listbook, which uses a ListCtrl to select pages within the Listbook. However, the width of the ListCtrl is less than the shortest page name. I would like to increase the width so that the page names are not truncated, but can't seem to.

Of course, I can access the ListCtrl using Listbook.GetListView(). However, changing the size has no effect. I also tried to access the sizer of the ListCtrl (via myListCtr.GetContainingSizer()) but that returns None.

How can I increase the width of the ListCtrl within a wx.Listbook?

I tried many solution from this task. I want testing axios instance api call without any libralies (jest-axios-mock, moaxios, msw, etc). I hope it's possible, because i succeeded testing simple axios call ( axios.get / axios.post without .create ) The main problem comes i tried testing axios instance call, i collides with three main errors on different attempts.

1 axios_instance_1.axiosInstance is not a function

2 Cannot read property 'then' of undefined

3 Cannot read property 'post' of undefined

I get this when i try bypassing module mock ( jestjs.io/docs/bypassing-module-mocks )

My last attempt looked like this

axios-instance.ts

I am using the MSW (Mock Service Worker) to mock the HTTP response in my react testing with react testing library. but, in some of the react components, I have some loading state until the response is fulfilled.

to test the intermediate loading state, is there a way to pause the ongoing service worker API and do some tests (do that we can ensure the consistency of the test) and then continue for further tests?

I need to make unit tests for some post requests but i dont understand how.I tried with mswjs but the test passes because i'm missing something and i dont know what.I tried to test the requests in an usual way but i wasnt able to put my conditions there and it was sending only 200 status code..
To start with,this is my folder structure:

I use next-redux-wrapper, MSW, @mswjs/data and redux-toolkit for storing my data in a store as well as mocking API calls and fetching from a mock Database.

I have the following scenario happening to me.

1. I am on page /content/editor and in the console and terminal, I can see the data was fetched from the mock database and hydrated from getStaticProps of Editor.js. So now IDs 1 to 6 are inside the store accessible.
2. Now I click on the PLUS icon to create a new project. I fill out the dialog and press "SAVE". a POST request starts, it's pending and then it gets fulfilled. The new project is now in the mock DB as well as in the store, I can see IDs 1 to 7 now.
3. Since I clicked "SAVE" and the POST request was successful, I am being routed to /content/editor/7 to view the newly created project.
4. Now I am on Page [id].js, which also fetched data from the mock DB and then it gets stored and hydrated into the redux store. The idea is, it takes the previous store's state and spreads it into the store, with the new data (if there are any).
5. Now the ID 7 no longer exists. And IDs 1 to 6 also don't exist anymore, instead, I can see in the console and terminal that IDs 8 to 13 were created, and the previous ones are no more.

Obviously, this is not great. When I create a new project and then switch the route, I should be able to access the newly created project as well as the previously created ones. But instead, they all get overwritten.

It either has something to do with the next-redux-wrapper or MSW, but I am not sure how to make it work. I need help with it. I will post some code now:

I have a small setup with webpack module federation, one container app and one remote. The remote is exposing itself completely and the container is consuming it to show it after clicking a navigation link like /users.

The container is reachable at localhost:8080, the remote at localhost:3001

Now, the remote is using mockup service worker (https://mswjs.io/), which works fine when visiting the app directly. When called through the container, an error comes up:

I have an app that fetches a list of users and displays them. The app works as expected but the test fails:

Users.js