Skip to content

Conversation

@lovelydinosaur
Copy link
Contributor

@lovelydinosaur lovelydinosaur commented Sep 29, 2016

  • Requests Client
  • API Client
  • Hypermedia support
  • API Client Uploads & Downloads
  • RAML Support & Docs
  • Schema fixes & Schema generation API
  • Validation codes
  • Technical error handlers
  • Fix 1.10 deprecation warnings
  • Add HTML_SELECT_CUTOFF, HTML_SELECT_CUTOFF_TEXT settings
  • Add SCHEMA_COERCE_PATH_PK, SCHEMA_COERCE_METHOD_NAMES settings.

  • API Client - Credentials.
  • API Client - Headers.
  • API Client & Requests Client - Documentation.
  • API Client & Requests Client - allow_external / reverse hosts etc.
  • Document client library uploads/downloads. - Let's just refer to the more complete docs.
  • Hypermedia support. (see Schema & Hypermedia follow ups #4241)
  • Validation error codes. (see Validation error codes with string like object #3775)
  • Finalize RAML support. (trailing slash, host name, docs, CSRF, login link, remove extra buttons, thank lynn root etc...)
  • Review Swagger support - examples/types, basePath/not at root, examples. (see Type annotations for CoreAPI #4384)
  • Review Django REST swagger integration.
  • Document RAML support.
  • Schema fixes & new schema generation API.
  • Document schema generation API. (And limitations)
  • Formalize get_schema_fields() API.
  • Document Cli, CoreJSON, CoreAPI.
  • Check remaining 1.10 deprecation warnings on tests.
  • Root node when using schemas (how to hyperlink?)
  • Schema view
  • Deprecation warnings (Both deal with those raised by Django 1.10, and move along any PendingDeprecation)
  • pk -> id in schema generation.
  • Media type for CoreJSON
  • Update schema examples. (New shortcut, and pk/id)
  • Deprecate Router init args for schemas.
  • Technical error handlers
  • Register views with routers
  • Review Schemas should automatically respect API root location #4401 "Schemas should automatically respect API root location"

@lovelydinosaur lovelydinosaur mentioned this pull request Sep 29, 2016
6 tasks
@lovelydinosaur
Copy link
Contributor Author

Okay, merging this to master now, since 3.5 will be the next release.
Some work outstanding, but that can happen as independant PRs.

@lovelydinosaur lovelydinosaur merged commit 0dec36e into master Oct 10, 2016
@lovelydinosaur lovelydinosaur deleted the version-3-5 branch October 10, 2016 12:03
@lovelydinosaur
Copy link
Contributor Author

Tracking remaining work on #4549.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants