1.1.0

feat: add visitor and pagination processors

This commit introduces two new processors: a visitor processor and a pagination processor.

The visitor processor generates code to manage and update properties of a model.
The pagination processor generates code to handle list-type properties.
The commit also includes updates to the ksp-common module to support the new functionality, and adds new annotations to the dynamic-pages-processor-annotations module.
These annotations are used to mark properties as visitable or paginateable.
Additionally, the necessary files and configurations are added to integrate the new processors into the project.

Add the visitor processor provider.
Add a new file to get extensions.
Add the paginate class.
Add the VisitorProcessorProvider class.
Add the necessary files to the visitor processor and the pagination processor.
Add new dependencies to the compose app.
Add the necessary ignore file.
Add a model class to manage pagination.
Add a model class to manage visitable data.
Add the PaginateModuleCreator class.
Add the VisitorModuleCreator class.
Add the VisitorProcessor class.
Update the ksp-common module to add a new constant and new extensions.
Update the dynamic-pages-processor-annotations module to add new annotations.
Update the setting file to add new modules.

1.05

Mapper processor improvements: Update dependencies, add option to include koin module, improve class name definition, and use ksp arguments

• Updates the dynamicPages and koin dependencies to 1.0.5 and 4.0.2 respectively.
• Adds a new option DP_INCLUDE_KOIN_MODULE to control whether to include the Koin module during processing.
• Introduces DefinitionNames for constants related to ksp arguments.
• Renames the prefix for modules to DP_MODULE_PREFIX.
• Adds DP_RENDER_MAPPER_ENGINE key to enable render mapper.
• Adds DP_INCLUDE_DEFAULT_SERIALIZER to enable default serializer.
• Adds koin module to render mapper if DP_INCLUDE_KOIN_MODULE is true.
• Use ksp arguments to define params.
• Add HomeTestResponseMapper and call it from AppContent to render.

1.0.4

Fix: Correct deep node mapper

This commit fixes an issue where the deep node mapper was not properly handling nested nullable types.

The following changes were made:

• Updated the logic to handle null values when extracting properties from a deep node.
• Added a new test case to verify the fix.
• Updated the documentation to reflect the change.

1.0.3

Fix: Correct deep node mapper

This commit fixes an issue where the deep node mapper was not properly handling nested nullable types.

The following changes were made:

• Updated the logic to handle null values when extracting properties from a deep node.
• Added a new test case to verify the fix.
• Updated the documentation to reflect the change.

1.0.2

First release