HN user

sktguha

22 karma

Frontend engineer, working in react and redux and JavaScript ,at Salesforce banglore, India

Posts13
Comments41
View on HN

The idea is similar to code snippets in vscode, but here the difference is you can specify any arbitrary node.js script to run.

So if you select some text in vscode and press a shortcut key , your script is given the selected text as first argument(and other options in second argument like absolutePath etc) and whatever is returned from your script , the selected text will be changed to that value

you could possible write an IDE plugin that hides the types information and only show them on hover etc. I don't think this reason is that strong of a point IMHO.

New JSX Transform 6 years ago

I mean of course, that would be nice. But the thing is modern editors like vscode will automatically convert class statements to className if you copy paste plain html from elsewhere. Don't know about other attributes though.

event sourcing is almost never a good idea

Wait isn't event sourcing the fundamental principle of redux ? And redux is the most popular UI state manager library out there. and why you feel event sourcing is not a good idea ?

you could try google recaptcha v3 which does not require any user input and runs in background. not 100% sure however if it helps in your case but i think it should definitely help

Regd the webext I wonder how it passes the props from client to background pages ? It is a real problem if the props are not serialisable. Note that this kind of problem would not be there in a single page client and redux store on same window context

Hi everyone , what is your opinion on gpt3 powered eslint in JavaScript coding , i.e enhanced potential issues detecting using gpt3. For example , in react redux connect if a person has passed ownprops in their mapstate to props however are not using it in returned values ,then it still causes a calling of the function on every render. Example:

connect(mapstateToProps, (dispatch,ownProps) => { console.log(ownProps) return {} }

// normal eslint check for unused variable will fail here

But with gpt3 it can detect that ownProps is not used in the returned object hence can flag it as potential issue

What other eslint rules can gpt3 enhance ?