Search and fix minor errors and typos

Development
21

Oh, I wouldn’t have thought of that in my life. I will correct the links in the last ticket this way and see how it works.

22

@dkayiwa As announced, this time the coreapps module. If you manage to find a few minutes to read the contents of the tickets, I will be very happy.

Tickets tasked with removing unused items from code. They do not have any effect on the operation of the code but improve its readability.

Tickets designed to improve the style of the code. They also have no effect on how the code works, but they look very bad.

Finally, tickets that can affect the effectiveness of the code.

All of these tickets are of very low complexity, just like the previous ones. I hope that they will help new volunteers enter the world of OpneMRS.

1 Like
23

Of course I will always have the time to go through your submissions. :slight_smile:

The tickets look good and i have made them ready for development. I noticed that you are becoming an expert in labelling and setting the ticket complexity. Leaving me with not more than just changing the status to ready for development. :grinning:

Will never get tired of saying, thank you! :slight_smile:

3 Likes
24

@dkayiwa Introductory tickets are disappearing faster than I thought. Additionally, I am closing TRUNK tickets as the release date of the new OpenMRS version is approaching, so it’s worth starting to organize its code.

However, in order not to run out of easy introductory tickets, I looked at the next module. This time I took care of the OpenMRS REST Web Services Module.

Below you will find several tickets, if you can find a few minutes, please check if any are suitable.

The first group - tickets that remove unused elements, old imports or forgotten variables from the code.

The second group - tickets that focus on elements that look ugly in the code, but their existence does not affect its effectiveness and operation.

Group three - tickets that not only look bad but in some situations can affect the code executed.

All tickets are set to low priority, however, if you find that a ticket requires a higher priority, please change it.

Hopefully, you won’t be angry with the number of tickets I have created, however, it would be difficult to group them otherwise.

1 Like
25

Thanks @sacull for continuing to do this! :slight_smile:

They are mostly low priority as you said. Though one of them looked like a bug.

I have made them ready for work. Can you also avoid adding a fix version? This is simply because it may not be done in the version you put on the ticket, hence creating a maintenance burden of having to change the fix version. We usually put the fix version when merging the code. Because then, you know the versions when it was actually done.

1 Like
26

I understand. I thought I’d help you by tagging the revision, and only added work for you. Now I understand what function this field has. I will not mess with this field in the future. :wink:

Thank you for your time.

1 Like
27

You have done very well at this. For each successive set of tickets, i do less than before, because you have already done for me the defaults. So keep this up! :slight_smile:

3 Likes
28

Thanks @sacull for this great contribution… Thanks once again :blush:

2 Likes