| "tailwindCSS.experimental.classRegex": [ | |
| // const foo = cn("...") | |
| // const foo = cx("...") | |
| // const foo = classnames("...") | |
| ["cn|cx|classnames\\(([^)]*)\\)", "[\"'`]([^\"'`]*).*?[\"'`]"], | |
| // <Component classNames={{ foo: "..." }} /> | |
| ["classNames=\\{([^}]*)\\}", "[\"'`]([^\"'`]*).*?[\"'`]"], | |
| // const foo = /* tw */ "..." | |
| ["/\\* tw \\*/ ?(.*)", "[\"'`]([^\"'`]*).*?[\"'`]"], | |
| // const foo = /* tw */ { bar: "...", baz: "..." } |
| import './index.css'; | |
| export default function App() { | |
| return <h1>Hello from Gist</h1>; | |
| }; |
| export const formatDate = (dateOrString, opts) => { | |
| const date = new Date(dateOrString); | |
| return new Intl.DateTimeFormat('pt-BR', opts).format(date); | |
| } |
tgit new fs/xyz [-b master]
git checkout master # ensure we are on master branch
git pull origin master --rebase # ensure master is up to date (fetch upstream && rebase)
git checkout -b fs/xyz # create the new src branch
git push -u origin @ # should we auto push new src branches to remote?
I. Should we auto push new src branches to remote? Maybe a opt-in flag?
| type ActionsBlock = { | |
| !type: 'actions' | |
| !elements: [ | |
| | StaticSelectElement | |
| | UsersSelectElement | |
| # | ConversationsSelectElement | |
| # | ChannelsSelectElement | |
| # | ButtonElement | |
| # | OverflowElement | |
| # | DatepickerElement |
Schema extracted from https://a.slack-edge.com/bv1-6-8cacda2/block-kit-builder.93ca53691de7cf9d4417.min.js
Probably the url/bundle will change every deploy so you might want to go https://api.slack.com/tools/block-kit-builder, open devtools and search for that file (block-kit-builder) in source tab. Pass some unminify tool and search for "JSON Schema".
PS1: Some block/element types simply does not work, idk why.
PS2: If you want to explore easily, copy the code and paste to the devtools console.
| outputs/* | |
| config.js |
| class OnlyInClient extends Component { | |
| static defaultProps = { fallback: null } | |
| state = { client: false } | |
| componentDidMount() { | |
| this.setState({ client: true }) | |
| } | |
| render() { | |
| if (!this.state.client) { |
Dan, there are bigger plans to redux this year?
Not sure what you mean 🙂 But I have no plans regarding Redux personally. I'm not actively involved with maintaining it.
Andrew Clark said on his Twitter that class components will be considered as legacy APIs in the future, while function components will remain. We must take this statement in consideration in the projects that are under development/will be developed? And what is the best way to write a component?
He also said on Twitter that we have dozens of thousands of class components and they aren't going anywhere 🙂 When/if we have a more convenient and less verbose way to declare components than classes, we'll definitely announce it, but I don't see how it could affect existing projects.
| // passing object to render with two fns (opener & content, for example) | |
| <Modal> | |
| {{ | |
| opener: ({ open }) => <button onClick={open}>Open Modal</button>, | |
| content: {{ close }) => <div><h2>Hi modal</h2> <button onClick={close}>Close me</button></div> | |
| }} | |
| </Modal> | |
| // passing as children array | |
| // https://stackblitz.com/edit/react-array-render-props |