Skip to content

Workarounds

Jump to bottom
Jay Roebuck edited this page Jul 9, 2022 · 4 revisions

This page is dedicated to storing some workarounds we had to use. Often times, we have to use workarounds to compensate for outdated libraries or other quirks in the project. Having this page to keep track of those will be good, so we can revert these workarounds whenever they are no longer necessary, or at least provide insight to onlookers as to why something 'weird' was done.

Replacing force_text with force_str in graphene_django

In Django 4.0+, force_text doesn't exist. Therefore, we simply need to replace the 2 usages of it in the graphene_django library. Possibly fixed by using release graphene-django==3.0.0b7 (which has been in beta for 1 year though...)

This workaround is used in:

Using CI=false during the build

When CI is true, since the compilation succeeds with warnings, the Github Actions workflow immediately shuts off and says the build fails. As a workaround we can use CI=false, which allows us to continue with CI despite the warnings. This may also be fixed in a future version of bootstrap (current: 5.1.3)

This workaround is used in:

Clone this wiki locally