일 | 월 | 화 | 수 | 목 | 금 | 토 |
---|---|---|---|---|---|---|
1 | 2 | 3 | ||||
4 | 5 | 6 | 7 | 8 | 9 | 10 |
11 | 12 | 13 | 14 | 15 | 16 | 17 |
18 | 19 | 20 | 21 | 22 | 23 | 24 |
25 | 26 | 27 | 28 | 29 | 30 | 31 |
- Interface
- solidity
- error
- SSR
- REACT
- JavaScript
- web
- 삶
- nextJS
- node.js
- Props
- blockchain
- graphQL
- middleware
- CSS
- bitcoin
- typeScript
- API
- tailwindcss
- Ethereum
- CLASS
- useState
- HTML
- 기준
- built in object
- hardhat
- evm
- Redux
- express.js
- concept
- Today
- Total
목록error (15)
ReasonJun
The require() function in Solidity is used to check for certain conditions before executing a function. If the condition passed to the require() function evaluates to false, the function will throw an exception and the transaction will be reverted. The require() function is typically used to check for valid input data or to verify that a certain state invariant is true. For example, the followin..
reference : https://kentcdodds.com/blog/wrapping-react-use-state-with-type-script Wrapping React.useState with TypeScript Stay up to date Subscribe to the newsletter to stay up to date with articles, courses and much more! Learn more Stay up to date Subscribe to the newsletter to stay up to date with articles, courses and much more! Learn more All rights reserved © Kent C. D kentcdodds.com
Problem : In the process of assigning the modified value in 'setTags' to the 'onChange' function, the value was updated one beat slowly. code: import React, { useState } from 'react'; interface ImageUploadProps { onChange: (value: string[]) => void; errors: any; } const TagInput: React.FC = ({ onChange, errors }) => { const [tags, setTags] = useState([]); const [tag, setTag] = useState(''); func..
In the part where you specify 'useForm', it is recommended to specify only one button: submit. If another button exists and it uses the lib as the useForm, submit will be executed. Instead of button, it is better to specify another div and set onClick.

While developing the web3 web app, the following error occurred during the metaMask linkage process. Currently, the metamask side has received the problem and the resolution is in progress. This error is solved once the metamask is disabled. Removing intrinsics.JSON.rawJSON Removing intrinsics.JSON.isRawJSON Removing intrinsics.%ArrayPrototype%.toReversed ... https://community.metamask.io/t/erro..
The "not assignable to parameter of type never" error in TypeScript occurs when you try to assign a value of a type that is not never to a parameter of type never. The never type is a special type in TypeScript that represents a value that can never occur. This means that any attempt to assign a value of type never to a parameter of type never will result in an error. For example, the following ..