Week Twelve

Week 12.


This week commenced and i fully worked on making sure all the hanging pull request with respect to the core have been merged and closed. I accomplished these by hastening up my speed in fixing reviews, then i created new branches called general fix where all the light works related to renaming adding exception modifying exception messages and as well writing tests.

Rest webservice.

After sucessfully finishing with the core and everything merged, I went straight away to the  rest webservice module where i added 2 endpoint to handle the get with provided activation and a post with new credentials  password and activation key. this i did before consulting my mentor and  after consulting him. There was alot of other design changes such. i had to send and email message to my two mentors ie primary mentor and backup mentor. I also posted on talk here  from this talk post i received many criticism and all of them were positively to my benefits in finishing up with the rest webservice first pull request on the restwebservice is located https://github.com/openmrs/openmrs-module-webservices.rest/pulls .  My backup mentor Burke assisted alot by providing with a sequence diagram  which is presented below.


Link to original image is passwordreset sequence diagram

Also the talk discussion for the design with respect to the webservice is starting as from https://talk.openmrs.org/t/gsoc-2018-reset-password-via-email-project/18066/22.


Todos,
Add the current changes and endpoint proposed in the sequence diagram.
Write Unit test for the endpoints.

Comments

Post a Comment

Popular posts from this blog

Algorithm Design A Call For Concern To Software Engineers

Image
Algorithms in its entirety are often misunderstood and misinterpreted by most of the software engineers or developers. Technically every software or program you develop does use an algorithm and in most cases brute-force that is the obvious solution and at times the easiest. In computer science and software engineering, the concern is in solving problems and any problem that needs to be solved requires a solution in a finite amount of time and using the smallest amount of resources as possible.  In this post is the discussion about the importance and need for a software engineer to be able and capable of designing a good algorithm in his or her software development lifetime. This post will also go further to demonstrate on the side effects that you as a developer have without basic knowledge of algorithms,  the software that you build and the community that uses the software you build. Importance of good algorithm design. Algorithm design is important because They make ...
Read more

A health wise peep into the life of a home based developer

First look at the lifestyle of a developer: Basically, a home-based developer though it applies to an office developer. It all begins with the lifestyle of the individual. Haven lived in this lifestyle and among other developers who equally lived a similar lifestyle, I can say the following.  Most developers take it as a lifestyle in that skipping breakfast is the order of the day and telling you that the last meal they take was maybe yesterday afternoon is a common wording that you can hear. This is not because they don’t have the means to get the food but most times because they neither felt hungry nor hadn’t any time to look for something and eat. This even goes further when they happened to get something and eat they eat what is termed junk food. Here I mean they go for what is readily available and takes less effort to acquire. They end up with things like bread, or just carbohydrate food. That is if we are to qualify it as food then they might spend their remaining time...
Read more