You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I found that the generation position is incorrect during use. For details, please refer to the comments in the code below. Thank you for taking the time to solve this problem. Thank you~
console.debug("lp ~ file: index.tsx:1 ~ SearchInput ~ _:",_)// This is wrong.import{Close,SearchasSearchIcon}from'@react-vant/icons'importclxfrom'classnames/bind'import{useState}from'react'import{Search}from'react-vant'importcssfrom'./index.module.scss'constcxBind=clx.bind(css)constSearchInput=(props: any)=>{// value stateconst[value,setValue]=useState('')console.debug('lp ~ file: index.tsx:19 ~ SearchInput ~ value:',value)const_search=()=>{props.onSearch(value)}return(<divclassName={cxBind('box')}><Searchbackground="#f2f3f5"className={cxBind('search')}value={value}onChange={(_)=>{_// Here, if using control+option+L, it will be generated at the top of the file.}}clearableonClear={()=>{setValue('')}}onSearch={_search}leftIcon={null}clearIcon={<Close/>}rightIcon={<SearchIcononClick={_search}/>}/></div>)}exportdefaultSearchInput
The text was updated successfully, but these errors were encountered:
Hi @beilo, thank you for reporting this issue and sharing a detailed example!
I’ve tested this scenario with the latest version of Turbo Console Log (v2.10.8), and it appears that the issue has been resolved. The generation location now works as expected.
Could you please update your extension to the latest version and verify if the problem persists? If it does, feel free to provide additional details, and I’ll be happy to investigate further.
Thanks again for taking the time to help improve Turbo Console Log and sorry for the very late response! 😊
I found that the generation position is incorrect during use. For details, please refer to the comments in the code below. Thank you for taking the time to solve this problem. Thank you~
The text was updated successfully, but these errors were encountered: