Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Purpose: This commit integrates the conversion of specific fields to boolean values in the find method to ensure consistent data representation when returning API data.
MySQL Boolean Representation: In MySQL, boolean fields are typically stored as integers, with 1 representing true and 0 representing false. However, for many API responses, it is preferable to return these fields as actual boolean values (true/false).
Automatic Conversion: The convertBooleanFields method is called after data retrieval and the afterFind event, ensuring that any specified fields are converted from 1/0 to true/false before the data is returned.
API Consistency: This conversion helps maintain consistency in API responses, aligning the data format with common expectations for boolean values in JSON and other data formats, where true and false are native boolean types.
Checklist: