Tag: Wrappers

Posted on

More into UI!

I was still working on the user interface for the past week as well.

I have as well updated the tests created previously by adding a new GoodsReceive. Such that the first scenarios of my major task is that when a user searches for a supplier from a purchase order, at the same time while creating a purchase invoice a goods received is created as well is almost 70% complete.

I also got to know that when retrieving properties or entities in EF core, we cannot mix Tracking and NoTracking, such that AsNoTracking() functions are used with method headers that contain the word “Read” as the method is only reading values from the database without getting tracked whether these values have been changed or not.

Likewise, method headers with Get are used when we want to track values in the database.

Wrappers are always involved with work that has to deal with the user interface. Meanwhile, services are involved with database work.

The Linq function Select() return a collection of items or elements, while, First() returns the first element that satisfies the condition.

See you all next week 🙂

Posted on

Wrappers, DAL and Pub/Sub

Basically, I get to learn new concepts and terms everyday at Tong Hin.

Last week, I got to know what DAL, Pub/Sub and decoupling mean.

I also got exposed to the reason why Wrappers are used instead of ViewModels. The reason is that Wrappers are used to hide the complexity of ViewModels and WrapperServices are used to hide the complexity of Wrappers. Such that programmers get access to the codings they need without having the need to go through the complexity that lies underneath the functions they are using.

Data Access Layer (DAL) is an interface which simplifies and gives access to data stored in persistent storage, it returns a reference to an object instead of returning a row of fields from the database. DAL is used to call methods such as insert, update and delete from methods in the class which would return objects that contain the needed values.

Pub/Sub which is also known as Publish-Subscribe is a software messaging pattern that allows messages to be sent from publishers to users (subscribers) without them getting involved in sending the message to the subscribers. The messages are sent to channels in which these channels are responsible of retrieving the messages from the publishers and sending them to subscribers.

On the other hand, coupling is defined as the level of interdependence among two software modules, thus, decoupling is the opposite, in which it means how unconnected two modules in a software program are found to be. Two software programs or modules are said to be decoupled when a change is done in one module, the other module does not need to be changed or in other words, the other module is not affected by the change that has occurred in the other module.

Lastly, I was taught how to create tests in a better and more efficient way. Instead of using Assert, Fluent Assertion is a better alternative to be used.

That’s basically a summary of what I have been through last week.

Wait for me next week again 🙂