moshthepitt / django-vega-admin Goto Github PK

#27 introduces a way to generate list view search forms.

However, these forms use the default FormHelper. We need to add a FormHelper class that is more specialised for search and that works with the generated form.

• date input widget
• time input widget
• date & time input widget
• date picker in badmin template
• time picker in badmin template
• date & time picker in badmin template
• select2 in badmin template
• phone number field (Update 17/6/2019 - wont fix)

Add an included, optional app, that uses vega_admin to add CRUD to Django users.

• get_form_actions
• get_form_helper_class
• get_default_formhelper
• get_layout

The action links rendered on each row should have the ability of being made dynamic.

Perhaps this can be achieved by extending render_actions_fn (or just making it configurable), maybe by making it take a function to check if action links should be rendered.

Add support for permissions to VegaCRUDView

make it possible to use urls that have slugs or uuids

You are likely to get an error like so django.urls.exceptions.NoReverseMatch: Reverse for 'plain-form-list' not found. 'plain-form-list' is not a valid view function or pattern name.

Add support for custom templates in VegaCRUDView default views.

Add support for configurable search fields in VegaCRUDView.

get_field_value will throw an error is the field is not hashable. e.g. for JSON field

Suggested fix:

    def get_field_value(self, field):
        """Get the value of a field."""
        if field.is_relation:
            try:
                return str(getattr(self.object, field.name))
            except AttributeError:
                return None
        try:
            # pylint: disable=protected-access
            return self.object._get_FIELD_display(field)
        except TypeError:
            # for some reason this is not hashable
            field_value = getattr(self.object, field.attname)
            return json.dumps(field_value, cls=DjangoJSONEncoder)

Add an example Django project that utilizes VegaCRUDView and can be run quickly to test this app.

In VegaCRUDView, we need to add custom configurable search and filter for list view, such that:

• you can define filter fields
• OR you can supply custom filter class
• add/configure search and filter form
• add a nice looking template for search and filter form

When you install this package the templates directory is not included

This is so that it does not conflict with any other apps out there that have the label "users".

This will be some kind of meta mothership of a view that tables at least a Model and generates view to create, update and delete the model objects. It should also generate url patterns that are already hooked up!

• Better looking form
• add support for date and time filters e.g. someField__year
• show search clearance button when any field is populated

Add support for login protection in some or all of the views generated by VegaCRUDView.

Right now cripsy form helpers are created inside get_modelform. We need to:

• decouple with get_modelform
• add a way to order fields
• add a way to use provided list of fields
• fix #46

Add a way to login protect some or all of the views in a CRUD view

When using a custom modelform, we need to have a way of making the form action buttons look similar to the native modelform buttons

Nothing is documented so far...

Add support for paginate_by in the list action of VegaCRUDView

__init__() got an unexpected keyword argument 'vega_extra_kwargs'

This happens when you create a CRUD view using a non-Vega model form.

The list view uses django-tables2

We need to add a way to autogenerate a TableClass for any model. The resulting table class should:

• show all fields by default
• allow specification of fields

Add bootstrap3 templates usable by VegaCRUDView

Add support for custom actions to VegaCRUDView.

Add a read/view action as one of the default actions in VegaCRUDView

• CreateView
• EditView
• ReadView
• ListView
• DeleteView

These should be generic class based view that should, in theory, work for any model that they are given

Make it easy to work with formsets.

See: https://dev.to/zxenia/django-inline-formsets-with-class-based-views-and-crispy-forms-14o6

https://docs.djangoproject.com/en/2.2/intro/reusable-apps/

• Add search form
• Add create new object button

Add a way to generate a crispy-form aware ModelForm for any provided model.

By default it should include:

• all editable fields
• back/cancel button
• ability to configure crispy forms options
• ability to provide a custom crispy forms helper

• Add ability to supply custom table for list view
• Add ability to add custom form for create view
• Add ability to supply custom form for update view
• Add ability to specify fields for list view
• Add ability to specify fields for create view
• Add ability to specify fields for update view