Closed bilgehanertan closed 11 months ago
Hey,
Thanks a lot for your contribution! We we're discussing this a bit and it seems a bit like a stop gap solution, one thing we were thinking of is adding an optional regex field or having regex be the default (although this would be a bit counter intuitive) to allow for future flexibility.
One major hurdle we have right now with anything relating to the database is future-migration, currently there is no easy way to make a structural changes to an existing database. This has the been the main thing preventing this issue from being solved.
Probably the best way forward would be to setup a database version system and accompanying migration scripts, but maybe it needs some more thought.
Currently a lot of people involved are rather busy, so development is quite slow (and is also why it took so long to respond to this, sorry).
Resolves issue #29
Added a new boolean field to the database,
flag_caseinsensitive
, which is an optional field that defaults to False.During the check, the flag is being checked accordingly.
Note the
Challenges-Example
repository needs to be updated accordingly; however, nothing will be broken since the new field is not a required one for challenges.