A light REST library for Django.

An HTTP PUT is a complete replacement of a resource, so I think it should use mapper._apply(), which expects all required fields to have values.

Additionally, there should probably be an ObjectPatchMixin for HTTP PATCH (with a def patch(..)) that uses mapper._patch() and behaves like the existing ObjectPutMixin.

I'll probably have time to make a PR for this, but wanted to hear if this implementation (ObjectPutMixin with HTTP PATCH behavior) was intentional or an oversight.

Lastly, I realize this is a backwards incompatible change, but it seems like a bug in its current implementation, since it doesn't match the HTTP spec:

• HTTP PUT
• HTTP PATCH

Thoughts?

As of 1.7, it's entirely normal to have a reference to an AppConfig class in INSTALLED_APPS.

Since nap tries to import everything in INSTALLED_APPS during autodiscovery, attempting to run a Django app using these AppConfig classes results in ImportErrors.

I have a commit written to address this but I believe some kind of logging might be a better way to handle this.

Since digattr looks for callables and attempts to call them, the new Django 1.7 managers which require a manager= keyword argument cause errors when digattr calls without any arguments.

i.e.:

• nap calls manager() (obj())
• manager looks for manager keyword argument
• Keyword argument is not present so a KeyError is thrown

Something that would allow lazy people like me to get a fast understanding (without having to read through all the documentation/code) of what's good and bad versus the other rest frameworks like tastypie and rest-framework

There are small typos in:

• docs/extras/http.rst
• docs/mapper/fields.rst
• docs/quickstart.rst
• docs/tutorial/mapper.rst
• docs/tutorial/mappers.rst
• docs/tutorial/views.rst
• src/nap/rpc/views.py

Fixes:

• Should read raisable rather than raiseable.
• Should read publishable rather than pubishable.
• Should read passed rather than pased.
• Should read from rather than fron.
• Should read composable rather than composible.
• Should read authenticated rather than authentencated.
• Should read assigned rather than assignd.

Semi-automated pull request generated by https://github.com/timgates42/meticulous/blob/master/docs/NOTE.md

I have a simple model with two fields, I'm using a ModelSerialiser and a ModelPublisher with ModelPublisher.patterns() for the URLConf. When visiting the page I get an error "unbound method list_deflate() must be called with LabSerialiser instance as first argument (got QuerySet instance instead)"

Traceback:
File "/home/siecje/virtualenv/ccafe/local/lib/python2.7/site-packages/django/core/handlers/base.py" in get_response
  114.                     response = wrapped_callback(request, *callback_args, **callback_kwargs)
File "/home/siecje/virtualenv/ccafe/local/lib/python2.7/site-packages/django/utils/decorators.py" in _wrapped_view
  99.                     response = view_func(request, *args, **kwargs)
File "/home/siecje/virtualenv/ccafe/local/lib/python2.7/site-packages/nap/publisher.py" in view
  45.             return self.dispatch(request, **kwargs)
File "/home/siecje/virtualenv/ccafe/local/lib/python2.7/site-packages/nap/publisher.py" in dispatch
  111.         return self.execute(handler)
File "/home/siecje/virtualenv/ccafe/local/lib/python2.7/site-packages/nap/publisher.py" in execute
  118.                 object_id=self.object_id,
File "/home/siecje/virtualenv/ccafe/local/lib/python2.7/site-packages/nap/publisher.py" in list_get_default
  335.         data['objects'] = serialiser.list_deflate(data['objects'], **serialiser_kwargs)

Exception Type: TypeError at /lab/
Exception Value: unbound method list_deflate() must be called with LabSerialiser instance as first argument (got QuerySet instance instead)

class Lab(models.Model):
    title = models.CharField(max_length=255)
    duration = models.FloatField(help_text=_("Duration of Lab in Hours"), blank=True, null=True)
    description = models.TextField(null=True, blank=True)

For some reason I had 'nap' in my INSTALLED_APPS and got this really confusing ImportError: No module named apps on Django 1.8. Removing default_app_config from nap/__init__.py fixed this, as does removing nap from the installed apps.

I wonder if it's possible to provide a better error by default (probably Django's job), or to remove the app config. If not feel free to close this.

Not sure if this is a bug, but if you try to call http.MethodNotAllowed() without any parameters it 500s. Passing an arbitrary parameter fixes it.

Eg this does not 500: http.MethodNotAllowed({'error':'error'})

This does: http.MethodNotAllowed()

Traceback;
[09/Dec/2015 10:11:34] ERROR [django.request:256] Internal Server Error: /api/team/eject/
Traceback (most recent call last):
  File "/Users/dre/Envs/gametraka_project/lib/python2.7/site-packages/django/core/handlers/base.py", line 132, in get_response
    response = wrapped_callback(request, *callback_args, **callback_kwargs)
  File "/Users/dre/code/gametraka_project/apps/teams/rest_views.py", line 74, in team_eject
    return http.MethodNotAllowed()
TypeError: __init__() takes at least 2 arguments (1 given)

When I issue a delete request to remove an instance, it is successfully deleted but the return code is 500. Looks like it's trying to get a field from the instance after it's been deleted?

Mapper + Model + Traceback: http://dpaste.com/1VJMX4P

If no api_name is defined in Publisher-class exception happens:

Traceback (most recent call last):
  File "<console>", line 1, in <module>
  File "/home/jtiai/projects/katulupa.fi/keywinkki-light/winkki_services/urls.py", line 25, in <module>
    url(r'^license_logs/', include(ExportEntryListPublisher.patterns())),
  File "/home/jtiai/.virtualenvs/katulupa.fi/local/lib/python2.7/site-packages/nap/publisher.py", line 68, in patterns
    name = cls.api_name
AttributeError: type object 'ExportEntryListPublisher' has no attribute 'api_name'

Publisher uses hard-coded output which looks like

{
    "meta": {},
    "objects": [{...},{...}]
}

It requires overriding both, get_page and list_get_default methods to produce different output. It should be much more straightforward

The examples in the docs about validation in mappers are not correct - at least, exceptions are raised when calling e.g. put_invalid in the way that is is shown in the docs. It is not clear what the errors parameter for put_invalid should actually be.

This is the example code I'm referring to:

[...]
         try:
             data >> profile_mapper  # This is shorthand for _patch
         except ValidationError as e:
             errors.update(dict(e))

         if errors:
             return self.patch_invalid(errors)

https://django-nap.readthedocs.io/en/latest/rest/index.html#example-updating-two-objects