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

Extract methods from tablescreen for reuse in modules for redpotion. #679

Merged
merged 4 commits into from
May 12, 2015

Conversation

markrickert
Copy link
Contributor

This is needed for the DataTableScreen. I may need some more methods, don't merge till I say go :)

* master:
  Adds :searchable to the whitelisted properties a cell can have.
  Version 2.3.1
  Minor tweak
  Added on_cell_created and on_cell_reused
  Minor formatting tweaks
  Created PM::TableScreen#set_up_accessibility, #editable? and moved tableView:commitEditingStyle:forRowAtIndexPath to a new PM::TableScreen::Editable module
  Added a spec for editable?
  Wrote the spec to test if the TableScreen has tableView:commitEditingStyle:forRowAtIndexPath
  Handle additional status_bar scenarios

# Conflicts:
#	lib/ProMotion/table/table.rb
* master:
  Adds tests for prepare_for_reuse and ensures that it's called before on_reuse
  More concise checking to see if web image managers are defined.
  Make sure prepareForReuse calls super.
  Adds support for SDWebImage and takes preference over JMImageCache
@markrickert
Copy link
Contributor Author

This is ready to go as far as I'm concerned. I haven't needed any other methods to be extracted in a few days.

jamonholmgren added a commit that referenced this pull request May 12, 2015
Extract methods from tablescreen for reuse in modules for redpotion.
@jamonholmgren jamonholmgren merged commit ef174d4 into master May 12, 2015
@jamonholmgren jamonholmgren deleted the extract-table-methods branch May 12, 2015 18:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants