django-form-button
Django admin extra buttons with form
Screenshots
Installation
You can install the package via pip:
pip install django-form-button
Usage
from django.contrib import admin
from django.forms import FileField
from django.forms import Form
from django.http import HttpRequest
from django.http import HttpResponse
from django_form_button import FormButtonMixin
from django_form_button import form_button
from .models import Account
class UploadForm(Form):
file = FileField()
@form_button("Upload Accounts", UploadForm)
def upload_accounts(request: HttpRequest, validated_form: Form):
file = validated_form.cleaned_data["file"]
return HttpResponse(file.name)
@admin.register(Account)
class AccountAdmin(FormButtonMixin, admin.ModelAdmin): # type: ignore
form_buttons = [upload_accounts]
License
This project is licensed under the terms of the MIT license.
Contributing
Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.
Contact
If you want to contact me you can reach me at pradishbijukchhe@gmail.com.
Metadata
Release files for django-form-button 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| django-form-button-1.0.0.tar.gz | 4.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_form_button-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 10.4 kB
Security for django-form-button 1.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.