In terms of a front end application using django views you can totall
implement angular, and do whatever you want. If you're proposing that the
backend be rewritten in angular, I think that is probably unnecessary
overhead for what the admin is supposed to do, and will make customizing it
cons
yes. really... bad idea.
I wanted to offer something similar to generation of hello world
angular2-app under API.
for example:
we connect django-rest-framework-jwt
(https://github.com/GetBlimp/django-rest-framework-jwt) in our project.
And a magic image to us angular service for work with API of
> Would you be able to support partial indexes as well?
I am not sure if I would be able to squash it in my GSOC timeline, but yes,
I will definitely incorporate it (afterwards, if not during my GSOC). It
should not be very hard to implement once I am able to make functional
indexes work.
On Wed, Mar 9, 2016 at 11:16 PM, akki wrote:
>>
>> Of course, this is a great thing to have. But I wonder if we can do
>> something to prevent pushing non-indexes to the indexes attribute of
>> Meta. Having Meta.indexes = [CheckTypeConstraint(foo__in=['foo',
>> 'bar'])] doesn't read correctly.
>
>
