Skip to content
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

Adding CHANGELOG #385

Closed
zetachang opened this issue Mar 28, 2015 · 5 comments
Closed

Adding CHANGELOG #385

zetachang opened this issue Mar 28, 2015 · 5 comments
Labels
Resolution: Locked This issue was locked by the bot.

Comments

@zetachang
Copy link

Is it possible to maintain a CHANGELOG for each release (or just use the github's builtin feature to describe what's new in each release)?

@ide
Copy link
Contributor

ide commented Mar 28, 2015

This would be really good for major releases that aren't drop-in upgrades for the old version. See hapi as an example of a project that does this well.

@vjeux
Copy link
Contributor

vjeux commented Mar 28, 2015

Yeah, we're going to have proper api releases with documentation in the future. But, in the next few days after the announcement it's better to move fast and ship often to fix critical issues that people are facing.

If you are curious, you can look at github changelog to see what changed

@leecade
Copy link

leecade commented Apr 17, 2015

👍

@jsierles
Copy link
Contributor

We have changelogs now here: https://github.com/facebook/react-native/releases

@jsierles
Copy link
Contributor

Better changelogs are on the way with the upcoming 2 week release process.

@vjeux vjeux closed this as completed May 29, 2015
jasongrishkoff referenced this issue Feb 24, 2017
Summary:
We really need a better list view - so here it is!

Main changes from existing `ListView`:

* Items are "virtualized" to limit memory - that is, items outside of the render window are unmounted and their memory is reclaimed. This means that instance state is not preserved when items scroll out of the render window.
* No `DataSource` - just a simple `data` prop of shape `Array<any>`. By default, they are expected to be of the shape `{key: string}` but a custom `rowExtractor` function can be provided for different shapes, e.g. graphql data where you want to map `id` to `key`. Note the underlying `VirtualizedList` is much more flexible.
* Fancy `scrollTo` functionality: `scrollToEnd`, `scrollToIndex`, and `scrollToItem` in addition to the normal `scrollToOffset`.
* Built-in pull to refresh support - set set the `onRefresh` and `refreshing` props.
* Rendering additional rows is usually done with low priority, after any interactions/animations complete, unless we're about to run out of rendered content. This should help apps feel more responsive.
* Component props replace render functions, e.g. `ItemComponent: ReactClass<{item: Item, index: number}>` replaces `renderRow: (...) => React.Element<*>`
* Supports dynamic items automatically by using `onLayout`, or `getItemLayout` can be provided for a perf boost and smoother `scrollToIndex` and scroll bar behavior.
* Visibility callback replaced with more powerful viewability callback and works in vertical and horizontal mode on at least Android and iOS, but probably other platforms as well. Extra power comes from the `viewablePercentThreshold` that lets the client decide when an item should be considered viewable.

Demo:

https://www.facebook.com/groups/576288835853049/permalink/753923058089625/

Reviewed By: yungsters

Differential Revision: D4412469

fbshipit-source-id: e2d891490bf76fe14df49294ecddf78a58adcf23
@facebook facebook locked as resolved and limited conversation to collaborators May 29, 2018
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Jul 23, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

No branches or pull requests

6 participants