This PR introduces two major improvements to LiteJsonDb

[Yusufibin]

1. Enhanced search functionality: Added support for substring and case-insensitive searches in the search_data method.
2. Configurable logging system: Replaced all print statements with a proper logging system using Python's logging module, allowing users to control log levels and output.

Changes Made

Search Improvements (modules/search.py and LiteJsonDb.py)

• Added optional parameters substring (default: False) and case_sensitive (default: True) to search_data.
• Updated search logic to support partial matches and case-insensitive comparisons while maintaining backward compatibility.
• Improved docstrings to document the new parameters.

Logging System (LiteJsonDb.py and all handler/modules files)

• Introduced a LiteJsonDb logger with console output for user messages.
• Replaced all print statements in handler/db_operations.py, handler/encrypt.py, handler/method.py, modules/search.py, modules/csv.py, and LiteJsonDb.py with appropriate logger calls (logger.error, logger.info).
• Preserved ANSI color codes in log messages for better readability.
• Logging is enabled by default when enable_log=True in JsonDB initialization.

Backward Compatibility

• All existing APIs remain unchanged; new parameters are optional.
• Default behavior matches the previous version (exact, case-sensitive search; console output for messages).

Testing

To test the changes:

1. Import the library: import LiteJsonDb
2. Create a database: db = LiteJsonDb.JsonDB(enable_log=True)
3. Add data: db.set_data('users/1', {'name': 'Alice', 'age': 30})
4. Test search:
   • Exact: db.search_data('Alice')
   • Substring: db.search_data('Ali', substring=True)
   • Case-insensitive: db.search_data('ALICE', case_sensitive=False)
5. Check console logs for messages (e.g., errors on invalid operations).

[codingtuto]

@Yusufibin Wow 🔥 what a contribution! We’ll all check this out 👀
Thanks @Yusufibin for these awesome improvements — enhanced search and clean logging system, that’s top-notch work 💪

[anonymmouscoder]

@codingtuto We're waiting

[Yusufibin]

@codingtuto et @anonymmouscoder, j’attends :-) J’aimerais aussi intégrer un tableau de bord optionnel : il n’ajoutera pas de poids supplémentaire et l’utilisateur pourra simplement l’afficher avec une seule ligne de commande.

[anonymmouscoder]

Ça prends du temps le review ?? On bouge les choses @codingtuto

[Yusufibin]

:) @codingtuto

[anonymmouscoder]

It's truly a joy to see someone fully focused and contributing to our project and it's really time for you to move on to becoming a key player for this repo. We're somewhat obligated to be transparent with you about our current situation.
Right now, we're juggling quite a bit with our daily commitments and workload. To keep things moving forward efficiently, we'd like to propose a 7-day review window for contributions and this will help us manage expectations on both sides while ensuring we can give proper attention to quality reviews.THANKS YOU VERY MUCH

[Yusufibin]

@anonymmouscoder Thanks for the update and honesty! I fully understand the situation. The 7-day review window is a solid plan. I'm standing by whenever you're ready to proceed. Thanks again!

[codingtuto]

Salut @Yusufibin,

Merci pour la PR ! Le concept est bon (search amélioré + logging), mais j'ai trouvé quelques bugs en relisant le code :

Problème dans handler/method.py : vous avez supprimé accidentellement la ligne types[key] = type(value) (ligne 36-42). Ça va casser la validation des types. Il y a aussi du code dupliqué à la fin avec un print() qui traîne.

Petite chose : les fichiers .pyc ne doivent pas être commités. Faut les mettre dans .gitignore et les supprimer de la PR.

Sinon l'idée du refactoring logging est top ! Si tu peux corriger ces points, ça sera bon à merger. Let me know si tu as besoin de précisions 👍