ApplicationArchitecture - add an abstract API to the Data layer follow up

[mpostol]

Thanks to @230443 and @aczyzews contribution we have an example of the abstract API for the Data layer - I have just merged the code to the master branch fixing issue #179.

Unfortunately, the code has one fundamental error that breaks a well-known rule. I will appreciate volunteers that are able to fix the problem. The proposed scenario:

• describe the problem answering to this discussion
• selected proposal I will convert into an issue
• I will create a branch for further development
• I will add anchors to the code to point out where to start
• you will fork or synchronize the repository
• after applying your proposal pr to the origin

I will wait for your proposal up to 27-04-2021 12 PM.

[mpostol]

The AppArchit5.00 branch has been created.

[mpostol]

I have added issue #186 related to this discussion. A picture should provide a hint, but the problem is not connected with the circular references because it is allowed inside a layer.

Let me stress the issue is labeled:

• bug - something is wrong and must be fixed
• enhancement - it is possible to improve the example
• refactoring - only unimportant changes are expected.

We should decide - what is your opinion. I will appreciate sharing it with us. 🤞

[mpostol]

From the attached diagram we may derive the following questions:

1. Provided that a type must be a member of one layer only the question is what layer the Console class is a member of?
2. Should the layering pattern (architecture) be applied also to the external libraries?

[mpostol]

A final solution has been added in ApplicationArchitecture - fix example #186.

[mpostol]

Let me inform you that new release 6.0 of the ApplicationArchitecture is available. It correctly implements mvvm design pattern.