0.0.1

[yurvon-screamo]

0.0.1 release

Goals

The current implementation has 3 goals.

• Ease of implementation in any project without limitation
• Providing an opportunity to describe any complex scheme
• Support for the current version asyncapi(with the possibility of updating to 3.0.0 after release)

Test summary

Based on the results of the check in my environment.

Using the library has become much more convenient, but there is not enough flexibility in implementation. Next, I will develop the library in the direction of tools WITHOUT attributes.

Сompleted part of the roadmap

1 priority

The main purpose of the stage works is to make it possible to describe an operation in 1 attribute without restrictions on the number of operations per method/class

• To dotnet 7

• To asyncapi 2.6.0

• Set required and nullable props to schema

• Give the opportunity to work with multiple operations in the one class/method

• Kill channel attribute:

  [SubscribeOperation("asw.tenant_service.tenants_history", OperationId = "TenantMessageConsumer", Summary = "Subscribe to domains events about tenants.", ChannelDescription = "Tenant events.")]
  public void PublishHelloWord(string content) { }

• Rework message attribute:

  [SubscribeOperation<BrokerHelloWorldDto>("asw.tenant_service.tenants_history", OperationId = "TenantMessageConsumer", Summary = "Subscribe to domains events about tenants.", ChannelDescription = "Tenant events.")]
  public void PublishHelloWord(string content) { }

  [Message(Title = "Hello world, i`m class")]
  public record BrokerHelloWorldDto(string content);

• Kill channel params attribute (auto detect parameters from channel name)

  [SubscribeOperation<BrokerHelloWorldDto>("asw.tenant_service.{tenants_name}", OperationId = "TenantMessageConsumer")]
  public record BrokerHelloWorldDto(string content);

• Redo the processing of multiple documents in the application (save default document with null name!!)

  [SubscribeOperation<BrokerHelloWorldDto>("asw.tenant_service.{tenants_name}", OperationId = "TenantMessageConsumer", DocumentName = "Foo")]
  [SubscribeOperation<BrokerHelloWorldDto>("asw.tenant_service.{tenants_name}", OperationId = "TenantMessageConsumer")]
  public record BrokerHelloWorldDto(string content);

• Rewrite usage docs:

  • Fast start guide
  • Description of the basic config in di
  • Description of the operation attribute (+ description of working with channel parameters)
  • Description of the message attribute
  • Description of working with multiple documents

• Nuget package

• Usability test on my environment
  Based on the results of the check in my environment. Using the library has become much more convenient, but there is not enough flexibility in implementation. Next, I will develop the library towards tools WITHOUT attributes.
  Example case:

    public void SubsribeApplication() {
        _js.SubByChannel<MyEvent1>("qwerty", _ => Console.Writeline("hello world"));
        _js.SubByChannel<MyEvent2>("qwerty.123", _ => Console.Writeline("hello world"));
        _js.SubByChannel<MyEvent3>("qwerty.zxc", _ => Console.Writeline("hello world"));
        _js.SubByChannel<MyEvent4>("qwerty.qwerty", _ => Console.Writeline("hello world"));
    }
    
    // ...
  
    private void SubsribeByChannel<TEvent>(this IJetStream js, string channel, Action<TEvent> handler) {
        // honestly, I want to define the operation here. 
        // example:
        // _operations += new PubOperation<TEvent>(channel);
        js.PushSubscribe(channel, (_, m) => handler(_parser.From(m.Msg.Data)));
    }

• Release !!

Known limitations of the version that will be received at this stage:

• There is no support for description and location for channel parameters from attributes (only from components ref)

---

This discussion was created from the release 0.0.1.