Skip to main content

Auto updating the play framework messages file for admin section

So the other day at work, my boss asked me to do a really boring task, which was to give meaningful names to some 30 to 50 labels in an html form i.e. I had to go in an manually type in proper names for all the labels in the form.

Ok a little bit of backstory, at work we have this large application that does all sorts of data processing and analysis amongst other things. Naturally the heart of this application is in the complex data processing tasks and therefore some UI aspects, only used internally by staff are largely ignored, well at least until there is time for it. The application is built using the play framework for Java and for the admin tasks, we use the auto admin generator provided by Play, that gives us the basic functionality. As those who have use Play framework would already know, when it generates the admin UI form, it maps the variable name to the field label in the html form. So for a class called Person with a property lastName, the admin generator code will generate a form with a label lastName. As you can guess, making these field names meaningful, really depend on who is using the application, however we had both the time and the motivation to do this. So the task fell on my very capable shoulders and I had the pleasure of doing this awesome task.

So in essence I had to update the conf/messages file with things such as "lastName=Last Name". Now for a class with 30 to 50 variables this is a lengthy task and the thought of it made me feel like I was working for Initech. So my solution to this? given that all our variables conform to the Java naming convention, I wrote a little method that used the Reflections API to split the variable name based on case and updated the messages file automatically.

The full source code for this method is over here.

Comments

Popular posts from this blog

Upload to AWS S3 from Java API

In this post, you will see code samples for how to upload a file to AWS S3 bucket from a Java Spring Boot app. The code you will see here is from one of my open-source repositories on Github, called document-sharing. Problem Let’s say you are building a document sharing app where you allow your users to upload the file to a public cloud solution. Now, let’s say you are building the API for your app with Spring Boot and you are using AWS S3 as your public cloud solution. How would you do that? This blog post contains the code that can help you achieve that. Read more below,  Upload to AWS S3 bucket from Java Spring Boot app - My Day To-Do (mydaytodo.com)

Addressing app review rejections for auto-renewing subscription in-app purchase (iOS)

The ability to know what the weather is like while planning your day is a feature of  My Day To-Do  Pro and as of the last update it’s also a part of the  Lite version . Unlike the Pro version it’s an auto-renewing subscription based  in-app purchase (IAP)  in the Lite version. What means is that when a user purchases it, the user only pays for the subscription duration after which the user will be automatically charged for the next period. Adding an  auto-renewing  subscription based IAP proved to be somewhat challenging in terms of the app store review i.e. the app update was rejected by the App Review team thrice because of missing information about the IAP. Therefore in this post I will share my experiences and knowledge of adding auto-renewing IAP in hopes to save someone else the time that I had to spend on this problem. In-App purchase This year I started adding IAPs to My Day To-Do Lite which lead to learning about different types of IAP...

Ionic app with a Django backend: Part 2 - The Ionic app

In this post, I will continue from where we left in Part 1 of this series.  In part 2, I will talk more about the front-end side of things. Ahh, I have a background in web development, hence I call this front-end, but that's not the most accurate thing to say in these modern times. So the right way to say this is, I will talk about the Ionic app in this Github repository(IonicAppWithRestBackend) in more details in this post. So what did we do in part 1? In part 1, we got to the point of running our backend on the web server that ships with Django . To refresh your memory, this is how we got the backend server running, Clone the repo git clone https://github.com/cptdanko/IonicAppWithRestBackend Navigate to the backend project directory cd IonicAppWithRestBackend/backend/python_django/restBackend/ Note: if you are using Windows, you may want to change "/" to "\" in the above command. Once there you can run the backend server with the follow...