New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Fiber] Umbrella for remaining features / bugs #7925

Closed
sebmarkbage opened this Issue Oct 10, 2016 · 10 comments

Comments

Projects
None yet
9 participants
@sebmarkbage
Member

sebmarkbage commented Oct 10, 2016

This is an umbrella issues for remaining fiber issues. More can be found by running the unit tests with the useFiber flag in ReactDOMFeatureFlags turned on

See #8830 for additional tasks beyond the scope of the initial Fiber release

Phases 1–6

Phase 1: Infrastructure

Phase 2: Smaller / Initial Tasks

  • ReactDOMFiber.render - Simple synchronous case. [@sebmarkbage] #8029
  • String refs using owner. [@acdlite] #8099
  • Pass the correct previous state to componentDidUpdate. #7941
  • componentWillMount, componentWillReceiveProps, componentWillUpdate life-cycles. [@sebmarkbage] #8015
  • componentDidUpdate should not fired if shouldComponentUpdate returns false. [@sebmarkbage] #8028
  • Instance should be recreated when already started work gets resumed (no componentWillReceiveProps without didMount). [@sebmarkbage] #8015
  • Fix module pattern in mountIndeterminateComponent. [@sebmarkbage] #8015
  • findDOMNode. #8083 [@sebmarkbage]
  • Switching between types doesn't track deletions (updateSlot doesn't return null). [@sebmarkbage / @gaearon] #8085
  • PureComponent flag. [@acdlite] #8118
  • Ensure that scheduling works synchronously by default but batched in DOM events. (Initial default priority.) [@acdlite] #8127
  • unstable_batchedUpdates [@acdlite] #8127
  • setState in componentDidMount/componentDidUpdate should always be synchronous at the end of the batch. Even if work is deferred. [@acdlite] #8206
  • Make sure setState + error boundaries work in it [@gaearon / @acdlite] #8193
  • Unmount failed trees before attempting to recover [@acdlite] #8304

Phase 3: Larger Tasks

  • Allow testing Fiber in Facebook web codebase [@spicyj]
  • Error boundaries. [@gaearon]
  • Context [@gaearon #8272]
  • DOM attributes/properties update. [@sebmarkbage]
  • DOM events - Plug in the event system. [@sebmarkbage]
  • renderContainerIntoSubtree - Preserve state and such. [@spicyj #8368]
  • [fb] Bug: Switching from text children to regular children won't clear the old text content. (Not an easy fix since the side-effect of the parent is scheduled after the child insertions.) [@acdlite / @sebmarkbage] #8331
  • Recover from errors during commit phase, including errors thrown from host environment. Should only use a single try-catch block. [@acdlite]
  • [fb] SVG mode switch (based on if a parent is SVG or HTML). [@gaearon #8417]
  • [fb] setState behavior when called in all possible life-cycles including sibling life-cycles and parents and children. [@acdlite]

Phase 4: Uncovered Bugs

  • Root container is wrong in commit phase (#8568 (comment)) [@sebmarkbage] #8607
  • Update state/props object pointers even if bailout happens. This will currently cause an unnecessary componentDidUpdate. Solve that somehow. [@acdlite] #8655
  • Validate if inputValueTracking does indeed need to be cleaned up on unmount I don't think it needs to but we should revert anyway
  • autoFocus doesn't work. Todo in ReactDOMFiberComponent. [@bvaughn] #8646
  • [fb] When the last effect renders, there's an infinite loop. [@acdlite]
  • [fb] Defer clearing of initial nodes until work is actually begun. (Ensure that unmounting and rerendering in the same batch works.) [@acdlite]
  • Updates on different roots in componentWillMount (ReactUpdates-test) [@acdlite]
  • Refs should update even if shouldComponentUpdate returned false. However, componentDidUpdate should not fire. [@acdlite] #8685
  • [fb] Make top level render and unmount synchronous by default even when they're in a batch. (Even for updates? No, not for updates.) [@acdlite] #8634
  • [fb] Uncaught TypeError: Cannot read property 'children' of null
    let nextChildren = workInProgress.pendingProps.children;
    (probably due to context change, based on the caller) We should probably either avoid rerendering or set pendingProps to memoizedProps in this case. [@sebmarkbage] #8613
  • Does replaceState remove any previous callbacks scheduled? [@acdlite]
  • Root fiber should use updateQueue instead of pendingProps. [@acdlite]
  • [fb] Ensure that we get the current props for controlled components in restoreStateIfNeeded. [@spicyj] #8443
  • [fb] Iterable children. (E.g. immutable.js / Set etc.) [@gaearon #8446]
  • [fb] Reuse HostText when bailing out [@sebmarkbage] #8371
  • [fb] Ensure that renderSubtreeIntoContainer twice enables the context to pass through the middle subtree. I.e. two nested layer with a single context provider at the very top. [@spicyj] #8407
  • Make HostContainer append/insert/remove child instead of always updating all. Detach .return when a child gets unmounted (removed). [@sebmarkbage] #8400
  • Handle selection restoration #8401 #8353
  • Swap out the active Fiber when a host node is updated - including if listeners change so that we can know which listener is active. This needs to remain even when prepareUpdate is fixed.
  • Remove traversal of .output. #8406
  • findDOMNode and findAllInRenderedTree are broken. If an insertion happens and we happen to look at the previous work in progress, then it will not have any deletes or removes. So it looks like it is current. I assume the same can happen for a deletion after it is done. [@sebmarkbage] #8450
  • [fb] Batch different roots together into one commit (ReactUpdates-test) Won't fix. Use Portals instead. #8508
  • Error handling when an error is thrown in detachRef callbacks. [@acdlite]
  • Ensure that if we walk up .return in TreeTraversal we always get the current Fiber for props, or possibly just walk up the parentNode tree instead. [@sebmarkbage] #8491
  • Ensure that when we switch on tag names, we cover mixed/upper case. E.g. React.createElement('INPUT'). Won't fix. Instead, we'll warn if upper case is used on HTML tags. [@sebmarkbage] #8563
  • Some scheduling issue is causing ReactCompositeComponentNestedState-test to fail. It performs the first setState before the second one. Will any of the Task priority stuff fix this? (@acdlite)
  • [fb] Scheduling an update during render doesn't work. We mostly already warn if setState is called from render, but it might required that componentWillMount (and others) calling a callback which sets state on a different component works. Currently the complete phase resets both the updateQueue and pending priority. This can cause infinite loops to happen. Apparently still used. We need to either warn/log better and upgrade everyone or support it in Fiber. [@acdlite]
  • Top-level context push/pop isn't properly matched up; lots of tests fail if you patch in this. #8568 [@bvaughn]
  • [fb] Reentrant mounting in synchronous mode [@spicyj #8623]

Phase 5

  • Feature flag to disable Fiber-only features [@acdlite] #8797
  • Polyfills or alternate paths for Map, requestAnimationFrame and requestIdleCallback. [@sebmarkbage] #8833
  • isMounted - technically not deprecated yet. #8083 [@sebmarkbage]
  • Top level render callbacks. Second argument to render. #8102 [@koba04]
  • Ensure that server rendering works using Stack when Fiber is enabled. [#8372]
  • Declarative portal API @gaearon #8386
    • Add tests for event bubbling (This will need to track #8117 for changes to how top level event listeners get attached.)
  • React Test Renderer support. (@iamdustan #8628)
  • React ART support. #8521 (@bvaughn)
  • Land basic React Native support in React repo. #8560 (@bvaughn)
  • Mark root renders during mount (perf testing) (see tests for "marks top-level updates") [@bvaughn] #8687
  • Merge callbackList onto the updateQueue instead of a separate field. [@acdlite] #8728
  • Separate priority level for state updates. #7457 [@acdlite]
  • Fix coroutine issue where Fiber is passed in user space and could become stale. [@sebmarkbage] #8840
  • DOM Dev Tools [@gaearon]

Phase 6: Unit tests and known bugs push

  • [fb] Fix findDOMNode bug when used in certain cases from componentWillUnmount. [@sebmarkbage, @acdlite] #8897
  • [fb] Provide ability to block event bubbling in portals [@spicyj]
  • Unit tests: ReactFragment-test invariants [@acdlite] #8890
  • Unit tests: ReactDOMProduction-test invariant [@acdlite] #8907
  • Unit tests: ReactEmptyComponent-test invariant [@acdlite] #8908
  • Ensure we replace throw new Error with invariant calls and they have sensible messages [@acdlite] #8926
  • Unit tests: ReactMount-test [@acdlite] #8919
  • Unit tests: ReactMultiChild-test (remove Map as children support in Stack) [@acdlite] #8911
  • Unit tests: ReactMultiChildText-test [@acdlite]
  • RN: Fix event bubbling regression. [@spicyj/@bvaughn]
  • Make sure Babel doesn't generate bad code (e.g. IIFE for let/const), maybe fork Babel plugin to throw [@spicyj]
  • RN: Land React update in fbsource with Fiber disabled [@sebmarkbage]
  • Verify Fiber works in IE on Facebook (Map / Set: open IE10/11 and make sure it works) [@spicyj]
  • [fb] Figure out Ads Image Cropper issue [@spicyj]
  • Unit tests: ReactDOMComponent-test [@acdlite] #8948
  • Unit tests: ReactComponentLifeCycle-test warnings (ex: fDN in render) [@acdlite] #8949
  • Allow assigning this.state in cWRP with warning [@acdlite] #9040
  • Unit tests: ReactStatelessComponent-test warning [@trueadm] #9043
  • Unit tests: refs-test [@trueadm] #9045
  • Make a new manual propTypes checker. [@acdlite] #9004
  • Unit tests: ReactCompositeComponent-test warnings (ex: setState in render) [@acdlite] #8950
  • Ensure "break on all/uncaught exceptions" works as expected in browsers [@acdlite] #8961
  • Investigate what modules and unit tests fail if we remove Stack [@trueadm] #9069
  • Quick investigation into FB require.js perf [@trueadm]
  • Quick investigation into Fiber bundle perf, cutting out extra dev-only code [@trueadm] #9096
  • [fb] Move .hidden check into hostConfig (https://fburl.com/m8juo29d, https://fburl.com/538fgu7g)

Phase 6.1: 15.5 Release

  • Warn (throw?) when doing an update on a container that was manually emptied outside of React (in stack, this mounted a brand-new tree; in fiber, it tries to apply an update and usually fails) [@keyanzhang, @sebmarkbage took over this] (blocks beta)
  • Extract propTypes into a separate npm package. Get prop-types package name. [@acdlite]
  • Unit tests: ReactContextValidator-test -- Pass the correct previous context to componentDidUpdate (or deprecate feature and remove test). [@bvaughn] #8631
  • [fb] Better fix to ReactART.Text.
  • Update warning when calling propTypes directly to refer user to checkPropTypes API
  • Docs updates for test utils and removed add-ons [@flarnie]

Phase 6.2: React Native Fiber

  • Reimplement Shallow Renderer without Stack dependencies [@lelandrichardson/@trueadm] #8982
  • RN: ensure we keep all important invariants (such as that text must be wrapped in <Text>) (does not block anything but we should do this)
  • Ensure that we call the FB specific warning module instead of the fbjs/lib/warning one in RN. [@spicyj] (doesn't block anything OSS, internal to FB)
  • Convert propTypes callers to use checkPropTypes. [@acdlite]
  • Deploy forwarding modules to react/lib/ReactCurrentOwner, react/lib/ReactComponentTreeHook, fbjs/lib/invariant, fbjs/lib/warning, fbjs/lib/ExecutionEnvironment, fbjs/lib/performanceNow, fbjs/lib/emptyObject, fbjs/lib/emptyFunction, fbjs/lib/shallowEqual. So that we can keep using providesModule in this repo until we have flat bundles. Or better yet: Do the inverse and switch to using CommonJS naming convention in www. [@sebmarkbage, @bvaughn]
  • See if we can codemod createStrictPropTypeChecker away and use exactShape instead. (doesn't block OSS release)
  • Release a new version of react-redux whose peer is compatible with 16-alpha. Update RN to use it. reduxjs/react-redux#629
  • Enable prepareNewChildrenBeforeUnmountInStack feature flag (one week after landing sync).
  • Codemod Flow errors yielded by properly typing findNodeHandle. (we added types and $FlowFixMe comments; good enough for now)
  • Redesign the host component "type", the type of host component refs and integration with NativeMethodsMixin to be upgrade compatible. [@bvaughn]
  • Make sure instanceProps in ReactNativeComponentTree doesn't leak. (@sebmarkbage, @bvaughn)

Phase 6.3: Flat Bundles/Rollup

  • Make React Perf work with Fiber (ReactPerf-test) [@gaearon] (Decided not to in favor of deeper timeline integration)
  • Unit tests: ReactComponentTreeHook-test [@gaearon]
  • Unit tests: ReactHostOperationHistoryHook-test [@gaearon]
  • Make a list of all internal React modules required by FB code
  • Come up with a better strategy for dealing with DEV code and make sure we don't ship it in prod
  • Change www sync script https://fburl.com/juffnc9d to run rollup using commonjs source
    • Shimming the required files (ex: ReactDOMInjection, warning)
    • Exporting a single bundle that exposes the internals we need
    • Make fowarding modules for ReactDOM/etc as well as internal modules
  • Convert OSS repo to ES6 modules (does not block release; nice-to-have follow up)
  • Make separate dev and non-dev build in one file for www (if (__DEV__) { ... all of React ... } else { ... all of React })
  • Convert OSS repo to rollup
  • Replace current Grunt/Gulp build system with a unified build system (maybe purely using Rollup)
  • Add Closure Compiler with ADVANCED and deal with mangling properly (does not block release; nice-to-have follow up)

Phase 7: Async-Compatible (does not block release)

  • Fix incremental regression (if it is a regression)
  • [fb] Fix resumeMountClassInstance so that newProps gets passed to construct class. Otherwise this.props can be null.
  • RN: Aborting async work or unmounting a tree due to an error leaks native views
  • Add cross-renderer support for portals (necessary for async ART)
  • ReactDOMFiber.render - Return the root instance from render even if priority is deferred. Test and cover incremental cases
  • Decide on replacing priorities with deadlines to fix starvation

Phase 8: Server-Side Rendering

  • What are we doing?
  • Unit tests: ReactRenderDocument-test (SSR) -- Reviving server rendered markup (including rendering into document and shadow DOM containers)

Phase 9: Improvements (does not block release)

  • The getPublicInstance internal API should consistently be used before exposing any stateNodes.
  • Key-warnings on fragments. [@flarnie]
  • Don't mark "update" effect on newly mounted components unless they have a componentDidMount life-cycle.
  • Add support to Enzyme for Fiber (airbnb/enzyme#1007)
  • Currently bailing out on equal props/state equality means that we still copy all of our children, and traverse all of them. Meaning that a parent with many children will still do a lot of work even if it bails out / "skips". If "pendingWorkPriority" on referred only to children, we would know if any children has additional work. [@acdlite] #8716
  • Unit tests: ReactDOMTextComponent-test -- .normalize() case
  • Reconsider the ContentReset flag. Is there a cleaner solution for clearing out text content / innerHTML? Such as changing the insertion order
  • Reconsider storing masked contexts on instances
  • Revert inputValueTracking and replace with different comparison strategy. getter/setters is slow and complicated. Subscription model isn't helpful for Fiber's goals. The principle of over listening to lots of events and diffing the value is sound. We haven't shipped in OSS yet so not too hard to fix -- This will probably get pushed back to 16/17
  • Fiber drops the lazy DOM insertion order. Is there a solution that isn't slow in IE11? Is it worth fixing or should we leave IE11 slow and wait for a fix in the browser? (related: #8417)
  • Follow up from previous task (#8728 (comment)): use a linked list for callbackList [@acdlite] #8752
  • Ensure that it is possible to resume "incomplete" parents without rerendering. A shallow reuse. Store it on memoizedProps. Resuming "completed" parents is already possible. [@acdlite] #8716
  • Move callback invariant closer to usage as requested in #8639 (comment)
  • Replace some invariants with warnings to help code size #8677 (comment)
@donnieflorence

This comment has been minimized.

Show comment
Hide comment
@donnieflorence

donnieflorence Oct 30, 2016

Things that I hope would also be appended to this list of features/bugs:

  1. Fixing context
  2. Making stateless functional components more performant
  3. Learning from inferno to provide stateless function components some lifecycle hooks
  4. Maybe revising/improving reacts legacy build step
  5. Try to cut down react size in the major rewrite

donnieflorence commented Oct 30, 2016

Things that I hope would also be appended to this list of features/bugs:

  1. Fixing context
  2. Making stateless functional components more performant
  3. Learning from inferno to provide stateless function components some lifecycle hooks
  4. Maybe revising/improving reacts legacy build step
  5. Try to cut down react size in the major rewrite
@sophiebits

This comment has been minimized.

Show comment
Hide comment
@sophiebits

sophiebits Oct 30, 2016

Member

@donnieflorence This is a list of things we need to do to get parity with the existing implementation. After we finish these we might look at adding new features.

Member

sophiebits commented Oct 30, 2016

@donnieflorence This is a list of things we need to do to get parity with the existing implementation. After we finish these we might look at adding new features.

@gaearon

This comment has been minimized.

Show comment
Hide comment
@gaearon

gaearon Nov 8, 2016

Member

How to Help

  1. Watch an intro to Fiber
  2. Read about it here and here
  3. Clone React repo
  4. Run REACT_DOM_JEST_USE_FIBER=1 npm test to run unit tests with Fiber
  5. Pick a failing test and try to fix it (unless it fits into a broader group claimed by someone in the first comment)
  6. Run scripts/fiber/record-tests to verify which tests are now passing with Fiber
  7. Submit a PR!

Note: Contributing is hard right now.

It will get easier once more pieces (e.g. DOM attributes and events) are in place. There will be a long trail of issues where community can really help. But if you're feeling adventurous, you can give it a go. Check out older Fiber PRs for inspiration and pieces of information. Example Fiber "easy" PR: #8156.

Member

gaearon commented Nov 8, 2016

How to Help

  1. Watch an intro to Fiber
  2. Read about it here and here
  3. Clone React repo
  4. Run REACT_DOM_JEST_USE_FIBER=1 npm test to run unit tests with Fiber
  5. Pick a failing test and try to fix it (unless it fits into a broader group claimed by someone in the first comment)
  6. Run scripts/fiber/record-tests to verify which tests are now passing with Fiber
  7. Submit a PR!

Note: Contributing is hard right now.

It will get easier once more pieces (e.g. DOM attributes and events) are in place. There will be a long trail of issues where community can really help. But if you're feeling adventurous, you can give it a go. Check out older Fiber PRs for inspiration and pieces of information. Example Fiber "easy" PR: #8156.

gaearon referenced this issue Dec 5, 2016

iamdustan added a commit to iamdustan/react that referenced this issue Dec 21, 2016

./scripts/fiber/find-errors to make future Umbrella task easier
In #7925 there is a task to:

> Ensure we replace errors with invariant calls and they have sensible
> messages

While it is likely a bit premature to begin that work, this script will
make it easier to find and replace the exact call sites to manage.

Usage:
``` sh
$ ./scripts/fiber/find-errors

```

``` sh
$ ./scripts/fiber/find-errors --quiet

```

iamdustan added a commit to iamdustan/react that referenced this issue Dec 21, 2016

./scripts/fiber/find-errors to make future Umbrella task easier
In #7925 there is a task to:

> Ensure we replace errors with invariant calls and they have sensible
> messages

While it is likely a bit premature to begin that work, this script will
make it easier to find and replace the exact call sites to manage.

Usage:
``` sh
$ ./scripts/fiber/find-errors

...lots of output...

src/renderers/shared/fiber/ReactFiberScheduler.js#921:
  throw new Error('No error for given unit of work.');

src/renderers/shared/fiber/ReactFiberScheduler.js#940:
  throw new Error('Invalid type of work.');

src/renderers/shared/utils/ReactErrorUtils.js#55:
  throw error;

All done.
Results:
6 errors
0 unmodified
380 skipped
0 ok
Stats:
error: 42
Time elapsed: 4.031seconds
42 throw statements to to convert to `invariant`

```

``` sh
$ ./scripts/fiber/find-errors --quiet

...lots of output...

src/renderers/shared/fiber/ReactFiberScheduler.js#780:
src/renderers/shared/fiber/ReactFiberScheduler.js#785:
src/renderers/shared/fiber/ReactFiberScheduler.js#921:
src/renderers/shared/fiber/ReactFiberScheduler.js#940:
src/renderers/shared/utils/ReactErrorUtils.js#55:
All done.
Results:
6 errors
0 unmodified
380 skipped
0 ok
Stats:
error: 42
Time elapsed: 3.728seconds
42 throw statements to to convert to `invariant`
```

iamdustan added a commit to iamdustan/react that referenced this issue Dec 21, 2016

./scripts/fiber/find-errors to make future Umbrella task easier
In #7925 there is a task to:

> Ensure we replace errors with invariant calls and they have sensible
> messages

While it is likely a bit premature to begin that work, this script will
make it easier to find and replace the exact call sites to manage.

Usage:
``` sh
$ ./scripts/fiber/find-errors

...lots of output...

src/renderers/shared/fiber/ReactFiberScheduler.js#921:
  throw new Error('No error for given unit of work.');

src/renderers/shared/fiber/ReactFiberScheduler.js#940:
  throw new Error('Invalid type of work.');

src/renderers/shared/utils/ReactErrorUtils.js#55:
  throw error;

All done.
Results:
6 errors
0 unmodified
380 skipped
0 ok
Stats:
error: 42
Time elapsed: 4.031seconds
42 throw statements to to convert to `invariant`

```

``` sh
$ ./scripts/fiber/find-errors --quiet

...lots of output...

src/renderers/shared/fiber/ReactFiberScheduler.js#780:
src/renderers/shared/fiber/ReactFiberScheduler.js#785:
src/renderers/shared/fiber/ReactFiberScheduler.js#921:
src/renderers/shared/fiber/ReactFiberScheduler.js#940:
src/renderers/shared/utils/ReactErrorUtils.js#55:
All done.
Results:
6 errors
0 unmodified
380 skipped
0 ok
Stats:
error: 42
Time elapsed: 3.728seconds
42 throw statements to to convert to `invariant`
```

@acdlite acdlite referenced this issue Jan 19, 2017

Open

[Umbrella] Async rendering #8830

5 of 17 tasks complete
@stefensuhat

This comment has been minimized.

Show comment
Hide comment
@stefensuhat

stefensuhat Feb 3, 2017

will you support bind context like VueJS?. So there is no need bind function manually.

stefensuhat commented Feb 3, 2017

will you support bind context like VueJS?. So there is no need bind function manually.

@acdlite

This comment has been minimized.

Show comment
Hide comment
@acdlite

acdlite Feb 3, 2017

Member

@ssuhat

This is a list of things we need to do to get parity with the existing implementation. After we finish these we might look at adding new features.

#7925 (comment)

Member

acdlite commented Feb 3, 2017

@ssuhat

This is a list of things we need to do to get parity with the existing implementation. After we finish these we might look at adding new features.

#7925 (comment)

@rchanou

This comment has been minimized.

Show comment
Hide comment
@rchanou

rchanou Feb 3, 2017

@ssuhat I think they explicitly decided against this a long time ago for being too "magical". Using the experimental property initializer syntax is a nice way to deal with it; you can also try a 3rd party plugin like react-autobind.

rchanou commented Feb 3, 2017

@ssuhat I think they explicitly decided against this a long time ago for being too "magical". Using the experimental property initializer syntax is a nice way to deal with it; you can also try a 3rd party plugin like react-autobind.

@acdlite

This comment has been minimized.

Show comment
Hide comment
@acdlite

acdlite Feb 3, 2017

Member

Aside from being "magical," the problem with autobinding is that there's a performance cost to binding methods, and it's wasteful to autobind the ones that don't need it.

Member

acdlite commented Feb 3, 2017

Aside from being "magical," the problem with autobinding is that there's a performance cost to binding methods, and it's wasteful to autobind the ones that don't need it.

@elyobo

This comment has been minimized.

Show comment
Hide comment
@elyobo

elyobo Feb 3, 2017

Something akin to Inferno's linkEvent would be good though, skipping binding while allowing data to be passed through. Often I find myself with code in a loop that would benefit from this, e.g.

<ul>
  {things.map(thing => (
    <li key={thing.key} onClick={() => this.doSomething(thing.id)}>{thing.something}</li>
  ))}
</ul>

Being able to drop the binding there would be nice.

elyobo commented Feb 3, 2017

Something akin to Inferno's linkEvent would be good though, skipping binding while allowing data to be passed through. Often I find myself with code in a loop that would benefit from this, e.g.

<ul>
  {things.map(thing => (
    <li key={thing.key} onClick={() => this.doSomething(thing.id)}>{thing.something}</li>
  ))}
</ul>

Being able to drop the binding there would be nice.

@sebmarkbage

This comment has been minimized.

Show comment
Hide comment
@sebmarkbage

sebmarkbage Feb 3, 2017

Member

Let's create a separate issue for any further discussions.

Member

sebmarkbage commented Feb 3, 2017

Let's create a separate issue for any further discussions.

@facebook facebook locked and limited conversation to collaborators Feb 3, 2017

@flarnie

This comment has been minimized.

Show comment
Hide comment
@flarnie

flarnie Jul 7, 2017

Contributor

We just moved remaining open items from 6.1-6.3 into #8854 and for now decided to archive this issue. We can open a new 'umbrella' issue or individual issues for items in phases 7-9 after we finish the 16.0 release.

Contributor

flarnie commented Jul 7, 2017

We just moved remaining open items from 6.1-6.3 into #8854 and for now decided to archive this issue. We can open a new 'umbrella' issue or individual issues for items in phases 7-9 after we finish the 16.0 release.

@flarnie flarnie closed this Jul 7, 2017

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.