ts-pattern | exhaustive Pattern Matching library for TypeScript | Functional Programming library

Article Avoid using the context.sync method in loops renders incredible help on the Word add-in I am developing. I see huge performance improvement after adopting the technique introduced in this article.

This really made my day. Now there is only one sync-loop left that I am not sure how to deal with it. Here is the sample code. The culprit function with context.sync() runs inside a loop, forming the sync-loop that drives me nuts. Any idea how to optimize it? For some reason, the two functions cannot be merged.

I need to translate my highcharts when the user selects a different language. I have a chartservice that listens to the translationService and assign the value received from translationService to downloadCSV attribute of chart. here is the code"

I would like to use pre-commit to handle git hooks for my git project. However, when I use it, the git commit command keeps to skip the unittest execution:

Situation:

To work with domain events, Jimmy Bogart proposed a method for storing events in aggregates.

This, from my point of view, is a very convenient approach. However, what about the case of a domain event in the domain service?

Domain Service should not have a state (stateless). In this case, in theory, the IDispatcher event dispatcher must be injected into the constructor of such a service.

Question:

To avoid introducing into the domain service of the event dispatcher, the suggested alternative approaches are correct:

1. Saving in the domain service of events of the last operation. However, this will violate the principle of stateless for the domain service.
2. Return the list of events from the service method based on the results of the operation (in the return method or in another way, depending on the capabilities of the programming language).

I've been working on a new document management project that uses DDD architecture. I'm new to DDD and event driven design, so it's been a learning experience.
My application is structured like this:

• MyProgram.Domain
• MyProgram.Infrastructure
• MyProgram.App
• MyProgram.WebApi

Domain has all of my domain logic, infrastructure is persistence, application is mostly commands and handlers, and the webapi is just the thing webapi.

Right now I'm working on implementing user authorization, and at the moment I've decided on using authorization handlers that will do permissions check before a command or query is executed. I think this gives me good flexibility perform complex resource-based authorization, since many of my permissions will depend on the current state of a certain entity.

So that is working out so far, I've implemented authorization in my application layer, leaving most of the user-specifics out of my domain model.

Now, the problem I'm trying to figure out is how to best include user information in my domain events, raised from my domain classes.

Example, I have a certain aggregate, let's say its document, and the document has a certain approval workflow. So when the document gets approved, I want to raise a domain event such as

I've implemented domain dispatching using a similar pattern here by overriding the SaveChanges method on my DbContext. I have entities with domain events that inherit a base abstract class that contains a list of domain events. I now want to enforce that the abstract class to have an Id property of a generic type.

Below is the base entity class before and after: