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

WM: get() docs should be specific about which method don't work with :content_file #219

Closed
spazm opened this issue May 8, 2017 · 0 comments · Fixed by #324
Closed

WM: get() docs should be specific about which method don't work with :content_file #219

spazm opened this issue May 8, 2017 · 0 comments · Fixed by #324

Comments

@spazm
Copy link
Contributor

spazm commented May 8, 2017

mark.sto...@gmail.com reported on Feb 4, 2013

The Mech docs for get() currently say:

" Because :content_file causes the page contents to be stored in a file instead of the response object, some Mech functions that expect it to be there won't work as expected. Use with caution."

Instead of the vaque "some Mech functions" language, the docs should be updated to state which methods do or do not work as expected. 

With the current vague docs, each user of :content_file is left to rediscover on their own trial and error which methods work with it, and which don't. 

  Mark

Details

Imported from Google Code issue 242 via archive

  • Type: Defect
  • Date: Feb 4, 2013
  • Reporter: mark.sto...@gmail.com
  • Owner: ----
  • Priority: Medium
  • Status: New
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 a pull request may close this issue.

1 participant