Add sample applications.

[fiseni]

Closes#344

The sample projects we had were outdated and overwhelming. Removed all of them. I created brand new sample apps, which are simple and easy to follow. Now that we have top-level statements, I added everything in a single file, so the consumers can clearly see the usage. Also, as library authors, we shouldn't have an opinion on how the users organize their solutions. That's one of the reasons I kept everything as simple as possible. There are 3 projects added:

• Sample.Domain - it's a common class library containing a few entities and specifications, so we can reuse them from the apps. Also, added a few specification extensions as an example.
• Sample.App1 - everything is included in Program.cs. This app demonstrates the basic usage of specifications. It uses the built-in repositories.
• Sample.App2 - It doesn't use the built-in repositories, there are custom implementations instead. I wanted to demonstrate how users can combine a few concepts and simplify overall usage greatly. These custom repositories contain methods for projecting directly to the API response models (conveniently available only for IReadRepository). The responses are automatically paginated and wrapped in PagedResponse. Also added examples of how to add custom evaluators. Btw, I use these repository implementations in my projects.

I think these samples cover most of the scenarios that are commonly used. But, in the future, whenever we want to demonstrate something additional, we may just add another project (e.g. App3 ) and focus on that given feature.

[fiseni]

Closes#344

The sample projects we had were outdated and overwhelming. Removed all of them. I created brand new sample apps, which are simple and easy to follow. Now that we have top-level statements, I added everything in a single file, so the consumers can clearly see the usage. Also, as library authors, we shouldn't have an opinion on how the users organize their solutions. That's one of the reasons I kept everything as simple as possible. There are 3 projects added:

• Sample.Domain - it's a common class library containing a few entities and specifications, so we can reuse them from the apps. Also, added a few specification extensions as an example.
• Sample.App1 - everything is included in Program.cs. This app demonstrates the basic usage of specifications. It uses the built-in repositories.
• Sample.App2 - It doesn't use the built-in repositories, there are custom implementations instead. I wanted to demonstrate how users can combine a few concepts and simplify overall usage greatly. These custom repositories contain methods for projecting directly to the API response models (conveniently available only for IReadRepository). The responses are automatically paginated and wrapped in PagedResponse. Also added examples of how to add custom evaluators. Btw, I use these repository implementations in my projects.

I think these samples cover most of the scenarios that are commonly used. But, in the future, whenever we want to demonstrate something additional, we may just add another project (e.g. App3 ) and focus on that given feature.

[fiseni]

Closes#344

The sample projects we had were outdated and overwhelming. Removed all of them. I created brand new sample apps, which are simple and easy to follow. Now that we have top-level statements, I added everything in a single file, so the consumers can clearly see the usage. Also, as library authors, we shouldn't have an opinion on how the users organize their solutions. That's one of the reasons I kept everything as simple as possible. There are 3 projects added:

• Sample.Domain - it's a common class library containing a few entities and specifications, so we can reuse them from the apps. Also, added a few specification extensions as an example.
• Sample.App1 - everything is included in Program.cs. This app demonstrates the basic usage of specifications. It uses the built-in repositories.
• Sample.App2 - It doesn't use the built-in repositories, there are custom implementations instead. I wanted to demonstrate how users can combine a few concepts and simplify overall usage greatly. These custom repositories contain methods for projecting directly to the API response models (conveniently available only for IReadRepository). The responses are automatically paginated and wrapped in PagedResponse. Also added examples of how to add custom evaluators. Btw, I use these repository implementations in my projects.

I think these samples cover most of the scenarios that are commonly used. But, in the future, whenever we want to demonstrate something additional, we may just add another project (e.g. App3 ) and focus on that given feature.

[fiseni]

Closes#344

The sample projects we had were outdated and overwhelming. Removed all of them. I created brand new sample apps, which are simple and easy to follow. Now that we have top-level statements, I added everything in a single file, so the consumers can clearly see the usage. Also, as library authors, we shouldn't have an opinion on how the users organize their solutions. That's one of the reasons I kept everything as simple as possible. There are 3 projects added:

• Sample.Domain - it's a common class library containing a few entities and specifications, so we can reuse them from the apps. Also, added a few specification extensions as an example.
• Sample.App1 - everything is included in Program.cs. This app demonstrates the basic usage of specifications. It uses the built-in repositories.
• Sample.App2 - It doesn't use the built-in repositories, there are custom implementations instead. I wanted to demonstrate how users can combine a few concepts and simplify overall usage greatly. These custom repositories contain methods for projecting directly to the API response models (conveniently available only for IReadRepository). The responses are automatically paginated and wrapped in PagedResponse. Also added examples of how to add custom evaluators. Btw, I use these repository implementations in my projects.

I think these samples cover most of the scenarios that are commonly used. But, in the future, whenever we want to demonstrate something additional, we may just add another project (e.g. App3 ) and focus on that given feature.

[fiseni]

Closes#344

The sample projects we had were outdated and overwhelming. Removed all of them. I created brand new sample apps, which are simple and easy to follow. Now that we have top-level statements, I added everything in a single file, so the consumers can clearly see the usage. Also, as library authors, we shouldn't have an opinion on how the users organize their solutions. That's one of the reasons I kept everything as simple as possible. There are 3 projects added:

• Sample.Domain - it's a common class library containing a few entities and specifications, so we can reuse them from the apps. Also, added a few specification extensions as an example.
• Sample.App1 - everything is included in Program.cs. This app demonstrates the basic usage of specifications. It uses the built-in repositories.
• Sample.App2 - It doesn't use the built-in repositories, there are custom implementations instead. I wanted to demonstrate how users can combine a few concepts and simplify overall usage greatly. These custom repositories contain methods for projecting directly to the API response models (conveniently available only for IReadRepository). The responses are automatically paginated and wrapped in PagedResponse. Also added examples of how to add custom evaluators. Btw, I use these repository implementations in my projects.

I think these samples cover most of the scenarios that are commonly used. But, in the future, whenever we want to demonstrate something additional, we may just add another project (e.g. App3 ) and focus on that given feature.

[fiseni]

Closes#344

The sample projects we had were outdated and overwhelming. Removed all of them. I created brand new sample apps, which are simple and easy to follow. Now that we have top-level statements, I added everything in a single file, so the consumers can clearly see the usage. Also, as library authors, we shouldn't have an opinion on how the users organize their solutions. That's one of the reasons I kept everything as simple as possible. There are 3 projects added:

• Sample.Domain - it's a common class library containing a few entities and specifications, so we can reuse them from the apps. Also, added a few specification extensions as an example.
• Sample.App1 - everything is included in Program.cs. This app demonstrates the basic usage of specifications. It uses the built-in repositories.
• Sample.App2 - It doesn't use the built-in repositories, there are custom implementations instead. I wanted to demonstrate how users can combine a few concepts and simplify overall usage greatly. These custom repositories contain methods for projecting directly to the API response models (conveniently available only for IReadRepository). The responses are automatically paginated and wrapped in PagedResponse. Also added examples of how to add custom evaluators. Btw, I use these repository implementations in my projects.

I think these samples cover most of the scenarios that are commonly used. But, in the future, whenever we want to demonstrate something additional, we may just add another project (e.g. App3 ) and focus on that given feature.

[fiseni]

Closes#344

The sample projects we had were outdated and overwhelming. Removed all of them. I created brand new sample apps, which are simple and easy to follow. Now that we have top-level statements, I added everything in a single file, so the consumers can clearly see the usage. Also, as library authors, we shouldn't have an opinion on how the users organize their solutions. That's one of the reasons I kept everything as simple as possible. There are 3 projects added:

• Sample.Domain - it's a common class library containing a few entities and specifications, so we can reuse them from the apps. Also, added a few specification extensions as an example.
• Sample.App1 - everything is included in Program.cs. This app demonstrates the basic usage of specifications. It uses the built-in repositories.
• Sample.App2 - It doesn't use the built-in repositories, there are custom implementations instead. I wanted to demonstrate how users can combine a few concepts and simplify overall usage greatly. These custom repositories contain methods for projecting directly to the API response models (conveniently available only for IReadRepository). The responses are automatically paginated and wrapped in PagedResponse. Also added examples of how to add custom evaluators. Btw, I use these repository implementations in my projects.

I think these samples cover most of the scenarios that are commonly used. But, in the future, whenever we want to demonstrate something additional, we may just add another project (e.g. App3 ) and focus on that given feature.

[fiseni]

Closes#344

The sample projects we had were outdated and overwhelming. Removed all of them. I created brand new sample apps, which are simple and easy to follow. Now that we have top-level statements, I added everything in a single file, so the consumers can clearly see the usage. Also, as library authors, we shouldn't have an opinion on how the users organize their solutions. That's one of the reasons I kept everything as simple as possible. There are 3 projects added:

• Sample.Domain - it's a common class library containing a few entities and specifications, so we can reuse them from the apps. Also, added a few specification extensions as an example.
• Sample.App1 - everything is included in Program.cs. This app demonstrates the basic usage of specifications. It uses the built-in repositories.
• Sample.App2 - It doesn't use the built-in repositories, there are custom implementations instead. I wanted to demonstrate how users can combine a few concepts and simplify overall usage greatly. These custom repositories contain methods for projecting directly to the API response models (conveniently available only for IReadRepository). The responses are automatically paginated and wrapped in PagedResponse. Also added examples of how to add custom evaluators. Btw, I use these repository implementations in my projects.

I think these samples cover most of the scenarios that are commonly used. But, in the future, whenever we want to demonstrate something additional, we may just add another project (e.g. App3 ) and focus on that given feature.