profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/django-crispy-forms/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.

django-crispy-forms/django-crispy-forms 4274

The best way to have DRY Django forms. The app provides a tag and filter that lets you quickly render forms in a div format while providing an enormous amount of capability to configure and control the rendered HTML.

django-crispy-forms/crispy-tailwind 102

A Tailwind template pack for django-crispy-forms

django-crispy-forms/crispy-bootstrap5 84

Bootstrap5 template pack for django-crispy-forms

django-crispy-forms/crispy-test-project 6

Simple Django project for testing https://github.com/maraujop/django-crispy-forms based on https://gist.github.com/maraujop/1838193

django-crispy-forms/crispy-forms-bootstrap2 0

Bootstrap2 templates for django-crispy-forms

fork NoahSandler/django-crispy-forms

The best way to have DRY Django forms. The app provides a tag and filter that lets you quickly render forms in a div format while providing an enormous amount of capability to configure and control the rendered HTML.

http://django-crispy-forms.rtfd.org

fork in 7 hours

issue commentdjango-crispy-forms/crispy-tailwind

Error when following the contributing process

That would be great thank you. 🙏

Not immediately obvious to why that's happening but looking more closely can wait. It seems sometimes just pinning things and leaving them a while can be the best approach. 🤷‍♂️

chriswedgwood

comment created time in 9 hours

issue openeddjango-crispy-forms/crispy-tailwind

Error when following the contributing process

I did the following:

forked and cloned python -m venv venv source ./venv/bin/activate (venv) pip install -r requirements.txt

image

Looking at the requirements file there isn't any pinning.

Will get a working version and then pin?

created time in 14 hours

starteddjango-crispy-forms/django-crispy-forms

started time in a day

starteddjango-crispy-forms/django-crispy-forms

started time in a day

starteddjango-crispy-forms/crispy-bootstrap5

started time in 2 days

starteddjango-crispy-forms/django-crispy-forms

started time in 3 days

starteddjango-crispy-forms/django-crispy-forms

started time in 3 days

issue commentdjango-crispy-forms/django-crispy-forms

1.12.0 Release broke radio buttons, check boxes

Hello, broken for me as well, using InlineRadios directly on a model field having choices. As a fix I downgraded to 0.11.2 😄

Would it be difficult to support the old behavior? Or at least raise an exception for the bogus usage..?

DanielSwain

comment created time in 3 days

starteddjango-crispy-forms/crispy-tailwind

started time in 3 days

fork Chukwuemeka-Mba/django-crispy-forms

The best way to have DRY Django forms. The app provides a tag and filter that lets you quickly render forms in a div format while providing an enormous amount of capability to configure and control the rendered HTML.

http://django-crispy-forms.rtfd.org

fork in 3 days

starteddjango-crispy-forms/django-crispy-forms

started time in 3 days

issue commentdjango-crispy-forms/crispy-bootstrap5

Default mb-3 in field.html may cause problems

Thanks for the comment

which is convenient in many cases,

I think this is what we have to aim for. That is, let's try and provide something that works for the most common use cases.

If you need something more custom then I think your always going to need something more bespoke, be it over riding a crispy template or in your own template. Happy to hear views on what else we could do here as I'm not sure. 🤔

GrandMasterInTheMask

comment created time in 3 days

issue openeddjango-crispy-forms/crispy-bootstrap5

Default mb-3 in field.html may cause problems

I'm talking about default behavior of creating div with class='mb-3' on every form field, which is convenient in many cases, but in my case it was a huge problem, since my form was in navbar, and i simple didnt need so big interval to bottom border. I haven't found acceptable solution (one idea i had is to overwrite field.html file and i decided to avoid it), and that leaded me to style this form without crispy. Everything else is great by the way.

created time in 3 days

starteddjango-crispy-forms/django-crispy-forms

started time in 5 days

starteddjango-crispy-forms/django-crispy-forms

started time in 5 days

starteddjango-crispy-forms/django-crispy-forms

started time in 5 days

starteddjango-crispy-forms/django-crispy-forms

started time in 6 days

starteddjango-crispy-forms/django-crispy-forms

started time in 6 days

starteddjango-crispy-forms/django-crispy-forms

started time in 7 days

issue commentdjango-crispy-forms/crispy-tailwind

Workflow/Configuration for purge

Okay this worked for me:

module.exports = {
  purge: {

   content: ['./**/templates/**/*.html','../envs/**/*.html'],
   safelist: ['underline','cursor-pointer','grid-cols-3','gap-1','grid-cols-2'],

}

In production my site-packages is under ../envs/.

The safelist is still required for class definitions defined in form Layouts e.g.

self.helper.label_class = (
            "font-noe text-sm font-normal leading-11 tracking-tight text-skin mt-6"
        )

Perhaps there is something we can do there to generate the safelist for those cases? What would be required dor this, a management command?

I'll add a documentation PR for this 👍

chriswedgwood

comment created time in 7 days

issue commentdjango-crispy-forms/crispy-tailwind

Workflow/Configuration for purge

Can we get the output from the search from tailwind/purge I wonder?

chriswedgwood

comment created time in 7 days

issue commentdjango-crispy-forms/crispy-tailwind

Workflow/Configuration for purge

Yes I did think about adding to the safelist. It wouldnt be that hard to generate it but it may make the config quite bloated.

Let me play around some more and I'll come back here with my findings/example.

chriswedgwood

comment created time in 7 days

issue commentdjango-crispy-forms/crispy-tailwind

Workflow/Configuration for purge

My initial thought is that maybe we could generate a safelist for the template pack. (These are the classes in use.)

chriswedgwood

comment created time in 7 days

issue commentdjango-crispy-forms/crispy-tailwind

Workflow/Configuration for purge

Hi @chriswedgwood hope you are well. Love your work on Django snippets. ♥️

Umm.. so... There's a purge option? 🕵️

I'm really happy to investigate but I've not come across this, I'm still learning lots about Django!

Maybe it is not possible but is there a small test project you could share that shows this issue?

Take care.

chriswedgwood

comment created time in 7 days

issue openeddjango-crispy-forms/crispy-tailwind

Workflow/Configuration for purge

Hi thanks for the project

I have an issue where I am using the purge option for my templates

module.exports = {
  purge: {

   content: ['./**/templates/**/*.html'],
   safelist: ['underline','cursor-pointer','grid-cols-3','gap-1','grid-cols-2'],

},

The css for the templates is not being applied when I deploy to prod If I am using the crispy template pack fields do I just need to add a path to my content that will be for the path to the templates in site packages?

created time in 8 days

starteddjango-crispy-forms/crispy-bootstrap5

started time in 9 days

starteddjango-crispy-forms/django-crispy-forms

started time in 10 days

starteddjango-crispy-forms/django-crispy-forms

started time in 10 days

starteddjango-crispy-forms/crispy-bootstrap5

started time in 10 days