search

elsa-workflows / elsa-core

A .NET workflows library
https://v3.elsaworkflows.io/
MIT License
6.58k stars 1.21k forks source link

Deprecated Dependency of AutoMapper.Extensions.Microsoft.DependencyInjection #4976

Open maximojgonzalezc opened 9 months ago

maximojgonzalezc commented 9 months ago

Currently, the Elsa.Core library has a dependency on AutoMapper.Extensions.Microsoft.DependencyInjection, which is being deprecated by the new version of AutoMapper. According to the AutoMapper upgrade guide, the functionality provided by AutoMapper.Extensions.Microsoft.DependencyInjection is now included in the main AutoMapper package, and the dependency should be removed. Technical Details

Deprecated Dependency: AutoMapper.Extensions.Microsoft.DependencyInjection Action Required: Remove the deprecated dependency and update the usage of AutoMapper in Elsa.Core to utilize the new compatible version.

Steps to Reproduce the Issue

Clone the Elsa.Core repository. Review the dependencies in the project configuration file. Note the presence of the deprecated dependency of AutoMapper.Extensions.Microsoft.DependencyInjection. Attempt to update AutoMapper to the latest version. Observe compilation errors related to the deprecated dependency.

image

image

glime-ai[bot] commented 9 months ago

Based on the context provided, it seems that you are reporting an issue with the Elsa.Core library having a dependency on a deprecated package, AutoMapper.Extensions.Microsoft.DependencyInjection. To address this issue, you would typically follow these steps:

  1. Fork the Elsa.Core repository on GitHub.
  2. Clone your fork locally.
  3. Open the project in your development environment.
  4. Update the csproj file to remove the deprecated dependency.
  5. Add the latest version of AutoMapper if it's not already included.
  6. Adjust the codebase to use the new AutoMapper functionalities as per the upgrade guide.
  7. Build the project to ensure that there are no compilation errors.
  8. Run tests to verify that everything is working as expected.
  9. Commit your changes with a clear and descriptive commit message.
  10. Push the changes to your fork.
  11. Create a pull request against the original Elsa.Core repository with a detailed description of the changes and the reason for the update.

However, since the context does not provide a direct link to the Elsa.Core repository or the AutoMapper upgrade guide, I cannot provide specific instructions or verify the exact steps needed for this update. If you have access to the repository and the upgrade guide, you should follow the steps outlined above and refer to the guide for any AutoMapper-specific changes.

If you encounter any issues or need further assistance, please provide additional details or clarify your request.