Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix obsolete crispy-forms references in UI styleguide #3227

Merged

Conversation

lunkwill42
Copy link
Member

@lunkwill42 lunkwill42 commented Nov 20, 2024

Fixes #3180

@podliashanyk may have other suggestions or improvements, but she's on vacation, and we want to remove the original wording before we make a new release. This can easily be improved further at a later date.

We don't use crispy-forms any more, but our internal form template
system mimics the subset of crispy-forms that we were once using.
We no longer use crispy-forms, so we don't have any "customizations"
of it.  Also, we never used Jabber, the IRC channel has been
discontinued and we prefer mailing lists to direct, person e-mails, so
this wording was also changed.
Copy link

github-actions bot commented Nov 20, 2024

🦙 MegaLinter status: ✅ SUCCESS

Descriptor Linter Files Fixed Errors Elapsed time
✅ PYTHON black 991 0 13.24s
✅ PYTHON ruff 987 0 0.1s

See detailed report in MegaLinter reports

MegaLinter is graciously provided by OX Security

Copy link

github-actions bot commented Nov 20, 2024

Test results

    9 files      9 suites   8m 31s ⏱️
2 139 tests 2 139 ✅ 0 💤 0 ❌
4 017 runs  4 017 ✅ 0 💤 0 ❌

Results for commit 2c1a9ae.

♻️ This comment has been updated with latest results.

python/nav/web/templates/styleguide.html Outdated Show resolved Hide resolved
There are many customizations done to the crispy forms. Basically, if you
need to create forms - ask on mail/jabber/irc.
Use existing forms as examples for how to build your own. If you have questions, ask them
on the NAV mailing lists or GitHub discussion forums.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
on the NAV mailing lists or GitHub discussion forums.
on the NAV mailing list or GitHub discussion forum.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we could even add a link to the discussion forum?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have multiple mailing lists. GitHub discussions has what I perceive as multiple forums per repo.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Contact details are documented elsewhere, I wouldn't want to repeat that here, but point to the relevant documentation.

Co-authored-by: Johanna England <[email protected]>
Copy link

sonarcloud bot commented Nov 21, 2024

Copy link

codecov bot commented Nov 21, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 60.39%. Comparing base (5937b2a) to head (2c1a9ae).
Report is 29 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #3227   +/-   ##
=======================================
  Coverage   60.39%   60.39%           
=======================================
  Files         605      605           
  Lines       43687    43687           
  Branches       48       48           
=======================================
  Hits        26383    26383           
  Misses      17292    17292           
  Partials       12       12           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.


🚨 Try these New Features:

@lunkwill42 lunkwill42 merged commit 2e45143 into master Nov 22, 2024
13 of 14 checks passed
@lunkwill42 lunkwill42 deleted the cleanup/fix-obsolete-crispyforms-refs-in-styleguide branch November 22, 2024 14:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

change styleguide wording so that is does not mention crispyforms anymore
3 participants