Add support for custom type mapping #30
Open
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.
In older Laravel versions,
database.phpconfig file containeddbalsection withtypeskey, which allowed to define custom database types. Starting Laravel 11, that section was removed and Laravel can retrieve custom database types from the database itself as string. Those are treated asmixedif not defined inDocumentationGenerator.php.This pull request adds back the same functionality - custom type mapping can be defined in config file.