#27622: Testing client should accept vendor tree json variants
-------------------------------------+-------------------------------------
     Reporter:  John Gresty          |                    Owner:  nobody
         Type:  New feature          |                   Status:  new
    Component:  Testing framework    |                  Version:  master
     Severity:  Normal               |               Resolution:
     Keywords:  json vendor          |             Triage Stage:
  testing_client                     |  Unreviewed
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  1                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by John Gresty):

 Replying to [comment:2 Tim Graham]:
 > I'm not familiar with vendor tree json variants. Could you explain that
 a bit more and give a use case in the Django ecosystem? Is it common
 practice and/or a standard?

 Vendor trees are defined in section 3.2 of RFC 6838
 ([https://tools.ietf.org/html/rfc6838#section-3.2]). My use case was
 trying to test a json api ([http://jsonapi.org]) implemented using
 [https://github.com/django-json-api/django-rest-framework-json-api] which
 returns the IANA registered content-type 'application/vnd.api+json'

--
Ticket URL: <https://code.djangoproject.com/ticket/27622#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.2a6319b75d1a2683bf4e56d2171520c4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to