link.js | module loader and conversion tool

This question goes into the rabbithole of material-ui, so its fine if you aren't interested, or can't understand.

In material ui, Buttonbase is root component of Button component, by default. You have overwritten it to your custom component Link, whose type (unlike ButtonBase) does not allow "variant" as its prop.

This is why type issue is occuring.

Solution? let Link component accept variant as props. Maybe add it to LinkProps. Its your choice

Sources https://material-ui.com/guides/api/#spread https://material-ui.com/api/button/

Assuming your JSON content has properties title and link, and that your click1 handler has been properly registered, you should be able to combine what you have into something like this:

It seems that is something that some folks have been experienced in https://github.com/react-csv/react-csv/issues/268 So you might try what they did to make it work.

If you want to send additional route parameters to the Nominate component then I suggest the following changes:

1. Edit the path='/nominate' path to accept a token parameter.

You should be using post to send data to server. Also you should be sending an object with email property in order to access it like req.body.email on the server.
Your code should probably be something like:

It seems like the code can't find your Link. Try running npm install and making sure the module is imported correctly.

Keep in mind that in your example each SideLink maintain their own independent state. When one of those call its own setactive, it doesn't have any effect on any other.

What I think you really want is one piece of state that live in a central location, the parent component, Sidebar, and forward to SideLink that value and the means to change that it.

The first thing you should do is read up on Promises. Promises are a way in JavaScript to encapsulate computations that are still ongoing. This is usually the case when you talk to an external service like a database or the operating system. They have been replacing callback style APIs.

In GraphQL a resolver can either return a value or a Promise that resolves to a value. This means, you can freely choose returning a value or a Promise, but if you call a database function like Prisma, you will get a Promise back, so you are kind of forced to stay "in Promise land", as there is no way to turn a Promise into a value. You can only chain functions, that should be executed with the value "in the future" (with then).

The last concept to understand is async/await. These async syntax is an addition to JavaScript syntax, that makes working with Promises easier. With await, you can stop the execution of a function until a value in a Promise arrives. Now, this looks like you are turning a Promise back into a value, but in reality, you function implicitly returns a Promise. For the VM to know about this, you have to state, that a function might use async by adding the keyword await in front of the function.

So when do you use async for a resolver? You could do it all the time, and the code would be correct. But doing it, even when you don't need to (e.g. you are not talking to a service) might have some performance implications. So it's better to only do it, if you really want to use the await keyword somewhere. I hope this can get you started with the concepts above, there is really a lot to learn. Maybe just go with your intuition and TypeScript errors until you deeply understand what is going on.

Yes, you can do that, this error happen since you are missing to wrap component via ...

If you like to put it for all project, you can simply do this: