jsx
Here are 4,433 public repositories matching this topic...
-
Updated
May 29, 2022 - Go
-
Updated
May 29, 2022 - JavaScript
The Storybook API has changed quite a lot since Solid's Storybook docs were written in 2019. It would be really helpful (and I think go a loooong way toward helping drive adoption, long-term) if Solid could:
- Update the docs to reflect the latest Storybo
-
Updated
May 27, 2022 - JavaScript
-
Updated
Nov 15, 2021 - JavaScript
For the most part this just works, but functions within tagged markup get weird indent assertions, e.g.,
${collection.map((item) => {
const { prop1, prop2 } = workWith(item); // eslint: expected indentation of 4 but found 10 (indent)
return html` // eslint: expected indentation of 4 but found 10 (indent)
<${Widget} prop1=${prop1} prop2=${prop2} />
Babel Macro
-
Updated
Apr 26, 2022 - JavaScript
I'm sorry to post an issue that is missing crucial evidence, but some debugging of a recent config loading bug makes me suspect that the react-rails railtie.rb may be modifying the load order of initializers, and preventing the values in Rails.application.config being as expected.
Whether this happens or not appears to be partly dependent on where in the Gemfile the react-rails gem is l
-
Updated
Mar 29, 2021 - JavaScript
We have an issue with the code generated for data that prettier doesn't format correctly.
It might be because of this .map((thisImport) => Object.keys(thisImport.imports).join(','))
Link to snap with the issue
BuilderIO/mitosis#3
-
Updated
Apr 28, 2022 - TypeScript
-
Updated
May 26, 2022 - TypeScript
-
Updated
May 29, 2022 - JavaScript
-
Updated
Apr 30, 2022 - JavaScript
Non-bubbling events
We should be able to use dispatchEvent to define callback prop based onevent APIs, so we don’t have to deal with capturing/bubbling for specific events.
function MyComponent({id}) {
const onclick = () => {
this.dispatchEvent(new CustomEvent("customclick", {detail: {id}}));
};
return (
/* children */
);
}// Usage
<MyComponent oncustomclick={(e-
Updated
Apr 29, 2022 - JavaScript
-
Updated
Nov 6, 2019 - JavaScript
-
Updated
May 25, 2022 - Emacs Lisp
-
Updated
Feb 11, 2022 - JavaScript
Blocked By: wix/vscode-glean#97
Example:
class Foo extends Component {
render() {
return (<div>
{this.props.foo.map((bar) => <div>{bar.x}</div>)}
</div>)
}
}
Current:
const Foo = props => {
const foo = useRef();
const x = useRef();
return <div>
{foo.current.map(bar => <div>{x.current}</div>)}
-
Updated
Apr 28, 2022 - JavaScript
-
Updated
Feb 11, 2022 - JavaScript
Improve this page
Add a description, image, and links to the jsx topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the jsx topic, visit your repo's landing page and select "manage topics."


This is about:
Component communication might deserve a dedicated page.
Ancestor -> Descendant
straightforward: passing props. Using a context if the descendants can be too deep down the tree.
Descedant -> Ancestor