Skip to content

[Internal] fetch API review #8865

@pavelfeldman

Description

@pavelfeldman

Release blocking

  • fetch name does not make sense for API testing, they want get, post, delete, etc.
  • postData should accept key/value pairs and end up with application/json encoding
    • there should be separate postData notation for application/x-www-form-urlencoded encoding
    • read header multipart/form-data and encode accordingly
    • postData is not a great name
  • should accept parsed query params
  • needs top-level shortcuts for popular headers, at least content-type and accept
  • add validate status option

Nice to have:

  • make API call without context
  • request.create() -> FetchRequest w/ cookie jar, settings
  • needs explicit ignoreHTTPSErrors
  • should retry requests (https://visionmedia.github.io/superagent/#retrying-requests)
  • make a series of API calls that produce storage state (cookies)
  • have default user-agent on the global fetch: Playwright/

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions