DEV Community ๐Ÿ‘ฉโ€๐Ÿ’ป๐Ÿ‘จโ€๐Ÿ’ป

DEV Community ๐Ÿ‘ฉโ€๐Ÿ’ป๐Ÿ‘จโ€๐Ÿ’ป is a community of 964,423 amazing developers

We're a place where coders share, stay up-to-date and grow their careers.

Create account Log in
Cover image for Creating custom services in medusa
Chris Bongers
Chris Bongers

Posted on • Originally published at daily-dev-tips.com

Creating custom services in medusa

Now that we know how to use an existing service in our routes. Let's take it to. The next level and see how we can create our service even.

A service is something that you can use throughout your application.

Let's say we want to add a translation service, for instance.
We'll have to open up our medusa server project and create a new file inside the src/services.

If our service is the translateService, we should name the file translate.js (filename without the Service part).

Creating a service in medusa

The most basic service file would look like this.

import { TransactionBaseService } from '@medusajs/medusa';

class TranslateService extends TransactionBaseService {
  func() {
    return '';
  }
}

export default TranslateService;
Enter fullscreen mode Exit fullscreen mode

As you can see, the service extends the โ€ŒTransactionBaseService, which gives us access to all the existing and other services.

Let's create a mock demo function so that we can give it a try.
With translations, we would need some mapping table, but let's mock it out for now.

const messages = {
  en: {
    title: 'Hello world',
  },
  nl: {
    title: 'Hallo wereld',
  },
};

class TranslateService extends TransactionBaseService {
  translate(msg, locale) {
    return messages[locale][msg] ?? msg;
  }
}
Enter fullscreen mode Exit fullscreen mode

This translate function will be able to translate specific messages into provided locales. If there is no match, the original message will be returned.

Using the custom service

Let's go ahead and see how we can use this custom service.
I'll use it in our custom routes as we already had a good intro.

Let's add a new route that will get our title.

router.get('/store/title', (req, res) => {
  const translateService = req.scope.resolve('translateService');
  const title = translateService.translate('title', 'en');
  res.json({ title });
});
Enter fullscreen mode Exit fullscreen mode

The first thing we do is retrieve our translate service, then we define a new variable for the title and request the title in a specific locale.
And eventually, return that.

Spool up your server and test out the route.

Medusa custom translate service

Now let's change the locale to nl and try it again.

const title = translateService.translate('title', 'nl');
Enter fullscreen mode Exit fullscreen mode

Medusa custom translate service

And you can even try to request a message that doesn't have any translations.

const title = translateService.translate('Products', 'en');
Enter fullscreen mode Exit fullscreen mode

Custom translate service fallback

And that's it. We now have a fully functional custom service in medusa.

Thank you for reading, and let's connect!

Thank you for reading my blog. Feel free to subscribe to my email newsletter and connect on Facebook or Twitter

Top comments (1)

Collapse
 
sindouk profile image
Sindou Konรฉ

Add to the discussion

Need a better mental model for async/await?

Check out this classic DEV post on the subject.

โญ๏ธ๐ŸŽ€ JavaScript Visualized: Promises & Async/Await

async await