Skip to content

Merge pull request #18 from AcademiaY4/feat/user-management #21

Merge pull request #18 from AcademiaY4/feat/user-management

Merge pull request #18 from AcademiaY4/feat/user-management #21

Triggered via push October 19, 2024 01:13
Status Success
Total duration 53s
Artifacts
build-and-deploy
42s
build-and-deploy
Fit to window
Zoom out
Zoom in

Annotations

10 warnings
build-and-deploy
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-dotnet@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build-and-deploy
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.
build-and-deploy: configuration/ServiceConfiguration.cs#L27
'FluentValidationMvcConfiguration.RegisterValidatorsFromAssembly(Assembly, Func<AssemblyScanner.AssemblyScanResult, bool>, ServiceLifetime, bool)' is obsolete: 'RegisterValidatorsFromAssembly is deprecated. Call services.AddValidatorsFromAssembly instead, which has the same effect. See https://github.com/FluentValidation/FluentValidation/issues/1963'
build-and-deploy: configuration/ServiceConfiguration.cs#L18
'FluentValidationMvcExtensions.AddFluentValidation(IMvcBuilder, Action<FluentValidationMvcConfiguration>)' is obsolete: 'Calling AddFluentValidation() is deprecated. Call services.AddFluentValidationAutoValidation().AddFluentValidationClientsideAdapters() instead, which has the same effect. For details see https://github.com/FluentValidation/FluentValidation/issues/1965'
build-and-deploy: Services/Impl/CategoryService.cs#L117
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
build-and-deploy: Services/Impl/CategoryService.cs#L123
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
build-and-deploy: configuration/ServiceConfiguration.cs#L27
'FluentValidationMvcConfiguration.RegisterValidatorsFromAssembly(Assembly, Func<AssemblyScanner.AssemblyScanResult, bool>, ServiceLifetime, bool)' is obsolete: 'RegisterValidatorsFromAssembly is deprecated. Call services.AddValidatorsFromAssembly instead, which has the same effect. See https://github.com/FluentValidation/FluentValidation/issues/1963'
build-and-deploy: configuration/ServiceConfiguration.cs#L18
'FluentValidationMvcExtensions.AddFluentValidation(IMvcBuilder, Action<FluentValidationMvcConfiguration>)' is obsolete: 'Calling AddFluentValidation() is deprecated. Call services.AddFluentValidationAutoValidation().AddFluentValidationClientsideAdapters() instead, which has the same effect. For details see https://github.com/FluentValidation/FluentValidation/issues/1965'
build-and-deploy: Services/Impl/CategoryService.cs#L117
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
build-and-deploy: Services/Impl/CategoryService.cs#L123
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.