django-formidable is a full django application which allows you to create, edit, delete and use forms.
Warnings
Python Compatibility : Python 2.7, 3.5
Django compatibility : Django 1.8, 1.9, 1.10
_Note: python3.4 support has been dropped since django-formidable 0.12.0._
License
MIT License
Documentation
Latest version of the documentation: http://django-formidable.readthedocs.io/en/latest/
If you want to build the documentation locally, you can try to run one of the following:
$ make docs
$ tox -e docsYou can also browse the documentation locally, using the following, for example:
$ make docs serve-docsQuick-Start
Install
$ pip install django-formidableConfigure
Define Roles
django-formidable allows access to a single form by different roles. The same form can thus be rendered in different ways. If you don’t need to handle multiple roles you must still define at least one default role.
Define a method which returns a list of formidable.accesses.AccessObject:
def get_roles(self):
return [
AccessObject(id='padawan', label='Padawan'),
AccessObject(id='jedi', label='Jedi')
]Fill the settings key:
FORMIDABLE_ACCESS_RIGHTS_LOADER = 'yourproject.access_rights.get_roles'Get context
While accessing a form for a specific role, you need to provide a way in which to get the correct context to use.
request and kwargs are fetched from the view (self.request, self.kwargs)
def get_context(request, kwargs):
return request.user.user_typeNext fill the setting key FORMIDABLE_CONTEXT_LOADER
FORMIDABLE_CONTEXT_LOADER = 'yourprojects.access_rights.get_context'Define URLs
URLs are defined in formidable.urls. You can load them with the following line:
url(r'^api/', include('formidable.urls', namespace='formidable'))By default, the views are not accessible, the permissions loaded are fully restrictive. To allow any access to the view fill your settings with
FORMIDABLE_DEFAULT_PERMISSION=['rest_framework.permissions.AllowAll']To handle special permissions, please refer to the online documentation.
7 maintainers
Metadata
7 maintainers
Release files for django-formidable 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 | Actions |
|---|---|---|---|---|
| django-formidable-1.0.0.tar.gz | 29.7 kB | Without provenance | Details for django-formidable-1.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| django_formidable-1.0.0-py2-none-any.whl | Python 2 | none | any | Details for django_formidable-1.0.0-py2-none-any.whl |
Total release size: 91.4 kB
Release files / django-formidable-1.0.0.tar.gz
| Download URL | django-formidable-1.0.0.tar.gz |
|---|---|
| Size | 29.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
572e6789563ab9a7fbe45675cc6d0433ec559735e287420635cf6240e0d2a240
|
|
BLAKE2b-256 checksum How to use checksums |
8d0c2b09188092a16f44917519068c910e177a487a7cb002c1b44f4b590ade8b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / django_formidable-1.0.0-py2-none-any.whl
| Download URL | django_formidable-1.0.0-py2-none-any.whl |
|---|---|
| Size | 61.7 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
4e3e620c7c85e76f4effe25b92185a0e07ceed351187c55cb61e22d6417fd53d
|
|
BLAKE2b-256 checksum How to use checksums |
7110f6d1b5fedd934c6aa165e3a9452d7ea3f6cd66d1984d32a79353f983252e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-formidable 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
