acm-udayton / acm-udayton/ACM-Meeting-Records

ENV boolean fields should not be strings

Open
#134 0 comments 0 reactions 2 assignees Claimed by @ethanlally View on GitHub
bug devops
Dominant language
Python
Stars
7
Forks
2
Avg merge
4d 23h
Merged PRs (30d)
2

Description

When reading from the .env file, all boolean values, `True`, `False` are automatically type-cast to strings by python. Initially the application was architected to just handle them as strings, but this is not ideal for future maintainability and extension of features.

This architecture should be revised so that they are truly booleans in the application logic and not string encapsulations of boolean values.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.