CODEWITHSUNDEEP
firefox
ganor
ganor

Reputation: 13

What is the "=>" operator?

In this link from MDN, it explains how to write a unit test for developing an addon for firefox. However, there are several segments that I don't understand and didn't find any useful result after searching google.

The first one, the following is a paragraph quoted from above link:

In a web page, you can perform Base64 encoding and decoding using the btoa() and atob() functions. Unfortunately these functions are attached to the window object: since this object is not available in your main add-on code, atob() and btoa() aren't available either. So we'll create a base64 module to expose these functions from the platform (see Creating Reusable Modules).

What does "the platform" in the above paragraph mean? the "Services.jsm"?

Also in the following code:

const { atob, btoa } = require("resource://gre/modules/Services.jsm");

this makes atob and btoa as one of the Services that is available for other class? or make (constant variables)atob and btoa both reference to the Services.jsm?

The Second one: what are these two lines of code do?

exports.atob = a => atob(a);
exports.btoa = b => btoa(b);

I understand the part

exports.atob

which enables atob function to be available from other classes outside the "base64.js". but what does the following mean?

= a => atob(a);

I didn't find that javascript has "=>" operator!

From my understaning, the reason we create a base64.js is because atob and btoa can only be called if we have the window object. Therefore we can use Services.jsm to get a reference of the window object?

Upvotes: 1

Views: 57

Answers (1)

Dexter
Dexter

Reputation: 2480

For "platform" in the paragraph you quoted they mean the set of functions which is not strictly Firefox browser code but rather implements basic, share functionalities. This usually lives in toolkit/modules in the mozilla-central repository. Services.jsm lives there as well so yes, that's part of the platform. Moreover, atob and btoa are both imported from Services.jsm.

The arrow => in exports.atob = a => atob(a); defines what's called an arrow function: it's a new, shorter syntax to define functions in JavaScript. This SO answer has many useful informations about it.

From my understanding, the reason we create a base64.js is because atob and btoa can only be called if we have the window object. Therefore we can use Services.jsm to get a reference of the window object?

That's almost correct: you need to export the function from the underlying platform as you don't have a window object there. If you had a window object, you would have just done window.atob or something like that. That call would have still called the same function you imported from Services.jsm.

So you're not using Services.jsm to get a reference to the window object, but rather directly importing the needed functions so that you don't need to have a window object.

Upvotes: 1

Related Questions