Using generator functions

Using generator functions

Generator functions are a new ES6 feature that allows you to write functions that can be exited and later re-entered. This can sometimes reduce the amount of code written to accomplish certain tasks.

Do not confuse the term generator function with generator. They are not the same. A generator function when invoked will return a generator which in turn can be used to produce values.

You can read more about this in MDN:

Generator function

Generator

Usage

This module accepts a generator function in many of its configuration properties. Experienced javascript users can take advantage of it to produce cleaner code.

They are supported in

• filename
• metadata
• identifier
• chunkSize
• root

The syntax is the same for all.

Here is an example:

const GridFSStorage = require('multer-gridfs-storage');
const storage = new GridFSStorage({
    url: 'mongodb://localhost:27017/database',
    filename: function* () {
      let counter = 1;
      while (true) {
        yield 'name' + counter;
        counter++;
      }
    }
});
var upload = multer({ storage: storage });

Notice the asterisk (*) after the function keyword. This is how you define a generator function. The previous example will run until it founds the yield keyword and will return the following expression pretty much like a return statement will.

The main difference is that the next time the module calls the generator it will continue its execution in the next line after the yield. In a normal function it would start at the beginning of the function body.

This allows the function to "remember" all its variables and values (it's execution context) exactly as they were before yield was called.

The output of the previous example will be

name1
name2
name3
....

If you try to write code to generate such values using standard functions, you will probably need help from global variables or similar workarounds.

Generators can be finite or infinite; that means they can produce some values until they reach certain condition or they will continue to produce values as long as they are called.

It is very important that you only write infinite generators.

If the generator is finished, then any file that comes next will fail to upload

FAQ

Q: Why is there an infinite loop on your example, isn't that a bad thing?

filename: function* () {
  ....
  while (true) {
    yield ....
  }
}

A: This is how you write an infinite generator function. This code will exit the function as soon as it reaches the yield statement. You can also write for(;;) {} or any other loop. As long as the yield is inside the loop and this continues to iterate indefinitely everything will be fine.

Q: I need the request and the file objects. How can I get those?

A: Generators work a little different than normal functions. The first time the generator is called you can access the values as the parameters like you normally would.

filename: function* (req, file) {
  ....
}

Remember that the execution resumes in the yield statement so the next value can be obtained as the result of the call

filename: function* () {
  let result = yield...
}

Here result is an object with the req and file properties.

This code sample reads the values on invocation and re-enter

const storage = new GridFSStorage({
    ...
    filename: function* (r, f) {
      let params;
      // the first loop will grab r and f
      // params is assigned on re-entry 
      let req = params ? values.req : r;
      let file = params ? values.file : f;
      ...
      params = yield 'name' + counter;
    }
    ...
});

Q: What happens if I finish the generator?

A: All subsequent uploads will fail with an error.

Q: Can I call return inside the generator?

A: Don't do that. This will finish the generator with the value returned. If you want to skip to the next iteration you can yield again.

Q: Can I yield a Promise?

A: Yes. Returning promises is supported in generators and regular functions.

Q: I tried to use a generator function but got an error. What happened?

A: You must have node version 6 or greater to use them. You also need version 1.2.0 or greater of this module.