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

Init without working range size #686

Closed
wants to merge 7 commits into from
Closed

Init without working range size #686

wants to merge 7 commits into from

Conversation

BasThomas
Copy link
Contributor

Changes in this pull request

Issue fixed: #414

Checklist

  • All tests pass. Demo project builds and runs.
  • I added tests, an experiment, or detailed why my change isn't tested.
  • I added an entry to the CHANGELOG.md for any breaking changes, enhancements, or bug fixes.
  • I have reviewed the contributing guide

What should we do with testing? I changed all the occurrences of the old initializer with the new one, so I think this is good to go?

@BasThomas
Copy link
Contributor Author

@ocrickard, @rnystrom thought you might be interested in looking at this as well.

@@ -103,6 +103,17 @@ IGLK_SUBCLASSING_RESTRICTED
workingRangeSize:(NSInteger)workingRangeSize NS_DESIGNATED_INITIALIZER;

/**
Initializes a new `IGListAdapter` object.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's add that this uses workingRangeSize 0

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also changed the opt-out to prefer the new init over providing 0 as a value.

@facebook-github-bot
Copy link
Contributor

@BasThomas updated the pull request - view changes

@@ -96,13 +96,26 @@ IGLK_SUBCLASSING_RESTRICTED
the previous and succeeding 2 objects will be notified that they are within the working range. As you scroll the list
the range is updated as objects enter and exit the working range.

To opt out of using the working range, you can provide a value of `0`.
To opt out of using the working range, use `initWithUpdater:viewController` instead.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suuuuuper nit: can this be

To opt out of using the working range, use initWithUpdater:viewController: or provide a working range of 0.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Of course!

@facebook-github-bot
Copy link
Contributor

@BasThomas updated the pull request - view changes

@facebook-github-bot
Copy link
Contributor

@BasThomas updated the pull request - view changes

Copy link
Contributor

@jessesquires jessesquires left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎉

@jessesquires jessesquires added this to the 3.0.0 milestone Apr 21, 2017
@facebook-github-bot
Copy link
Contributor

@jessesquires has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

@BasThomas BasThomas deleted the init-without-working-range-size branch April 22, 2017 18:45
facebook-github-bot pushed a commit that referenced this pull request May 9, 2017
Summary:
Issue fixed: -

Seem to have referenced the issue instead of the fixing PR during #686.
Closes #727

Differential Revision: D5032377

Pulled By: jessesquires

fbshipit-source-id: 76ae9b13e6912d8771f413c2f0f3c81e1df42304
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Remove workingRangeSize from initializer
4 participants