sitkoru / sitko.core Goto Github PK

Sitko.Core is a set of libraries to help build .NET Core applications fast

Home Page: https://github.com/sitkoru/Sitko.Core

License: MIT License

C# 95.02% HTML 4.44% CSS 0.37% Batchfile 0.02% JavaScript 0.15%

asp-net-core microservices dotnet grpc nats-streaming hacktoberfest blazor entity-framework-core serilog s3 automapper consul identityserver4

sitko.core's Introduction

Sitko.Core

Opinionated framework on top of .NET 8 and ASP.NET Core for building microservices.

Provides base application and modules for fast application building.

Modules

Logging
Tracing
Service discovery
Database access
Search
Queue
GRPC
Storage
Email
Unit testing

Using

See demo app for now

sitko.core's People

Contributors

Stargazers

Watchers

Forkers

moayyaed anhgeeky thevilshadoww igoralymov eneyer fredatgithub irac-ding ikvm lebatuananh jonyhuang mosesparadise dotnettreasury yassinebennani

sitko.core's Issues

Move Razor Renderer out of Mail project

Razor renderer can be used outside of mail module. We must move it to separate project or to App or App.Web.

Add support for .NET 5

.NET 5 will release in november. We can already start testing on it to be ready for release.

Application name and version should configurable

We should make Application name and version configurable via IOptions pattern. Maybe Application options can be defined via generic.

Add metadata support to Storage module

We need ability to store metadata alongside files in storage such as filename, image dimensions, etc. For S3 https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingMetadata.html can be used. For filesystem - additional metadata file seems like simplest way.

Add query params parsing to BaseComponent

Add helper methods to parse query string params

Rework apps and modules to support dynamic configs

We need to improve out configuration experience.

We need to support implicit configuration via IConfiguration
We need to support changes of configuration in runtime
We need support for some remote configuration sources like Vault

Fix public builds

Builds are failing after repository was made public

Broken attachments in mail

When mail has more than one recipients only first one gets attachments correctly. All other recipients will receive empty files.

SourceLink

Надо подключить поддержку SourceLink для удобного дебага

Repository not detect changes when new entity added to collection

If ItemA has collection of ItemB and we add new ItemB to collection, to when UpdateAsync(itemA) no changes detected.

Add traverse support to Storage module

It would be great to have ability to traverse storage like tree, get list of files and folders.

Публикация PHP-пакетов

Надо настроить публикацию PHP-пакетов куда-нибудь.

The automated release is failing 🚨

🚨 The automated release from the `master` branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

The release `10.0.0` on branch `master` cannot be published as it is out of range.

Based on the releases published on other branches, only versions within the range >=9.20.1 <10.0.0 can be published from branch master.

The following commits are responsible for the invalid release:

Merge pull request #725 from sitkoru/beta (34a62c6)
fix(grpc): fix for empty environment on grpc service in consul (89fa171)
fix(ci): set postgres hostname for new dbcontext (70de73c)
feat(dbpostgres): tmp fix for dotnet/efcore#29859 (8fb9f12)
fix(elasticstack): return EcsTextFormatter metadata (ba5543d)
fix(grpc): return back Result factory (25eee62)
reactor: code cleanup (76289a5)
feat: upd deps (2a5c751)
Merge pull request #742 from sitkoru/blazor/form-templates-rework (963b593)
Merge pull request #735 from sitkoru/grpc/remove-inheritance (c206053)
Merge branch 'master' into beta (07c724b)
feat(demo): upd forms demo (7c4bfa8)
feat(blazor): rework forms templates (8488455)
feat: support ef7 ExecuteUpdateAsync (fa5c76d)
feat: support ef7 ExecuteDeleteAsync (f1306fd)
Merge branch 'master' into beta (81bdfe4)
feat(grpc): drop inheritance, use composition (65f327a)
fix(mudblazor): remove obsolete (d2fed71)
refactor: code cleanup (18a9c03)
feat: .net 7.0.1, .net 6.0.12, upd deps (e6221fb)
Merge branch 'master' into beta (12fd1ce)
feat(consul): use app environment for service discovery (ddcbc07)
refactor: fix merge bug (412e926)
fix(ci): .net 6 and 7 for codeql (1bdabb9)
tests: fix resources name after interface renaming (05727e7)
fix(nats): method becomes static (9c45146)
test(repository): rollback refactor changes (e79578d)
refactor: code cleanup (7b69045)
fix(logging): don't skip enrichers, add env to logs (36c2f8f)
feat(app): add EnvironmentName app options to define current deployment environment (80a9a68)
feat(demo): upd demo to 7.0 (f38b510)
feat: .NET 7 (113f2dc)

Those commits should be moved to a valid branch with git merge or git cherry-pick and removed from branch master with git revert or git reset.

A valid branch could be next.

See the workflow configuration documentation for more details.

Good luck with your project ✨

Your semantic-release bot 📦🚀