Custom ImageOptions for each url (URL-level options)

[fityannugroho]

The idea is to provide ImageOptions settings for each url. User can pass an object into imgdl function that as the first argument. That object must contains the image url as the key, and the ImageOptions as the values. For example:

imgdl({
  'https://example.com/image.jpg': { name: 'myimage' }, // Will be saved as 'myimage.jpg'
  'https://example.com/image2.jpg': { extension: 'png' }, // Will be saved as 'image2.png'
  'https://example.com/image3.jpg': { directory: 'images' }, // Will be saved in 'images' directory
  'https://example.com/image4.jpg': { name: 'myimage', extension: 'png', directory: 'images' }, // Will be saved as 'myimage.png' in 'images' directory
});

This URL-level options will overrides any ImageOptions values in the second argument of imgdl (function-level options). For example:

imgdl(
  // URL-level options
  {
    'https://example.com/image.jpg': { name: 'myavatar' }, // Will be saved as 'myavatar.png'
    'https://example.com/image2.jpg': { extension: 'webp' }, // Will be saved as 'avatar.webp'
    'https://example.com/image3.jpg': { directory: 'avatars' }, // Will be saved as 'avatar.webp' in 'avatars' directory
    'https://example.com/image4.jpg': undefined, // Will be saved as 'avatar.png'
  },
  // function-level options
  {
    name: 'avatar',
    extension: 'png',
    // ... another options (`onSuccess`, `timeout`, etc.)
  },
);

---

UPDATE:

Considering the possibility of use cases where users download images from the same url and want to save it with different attributes (names, extensions, or directory locations), we decide to use array of objects rather than objects. For example:

imgdl(
  [ 
    { url: 'http://example.com/image.jpg', name: 'myavatar' }, // Will be saved as `myavatar.png` 
    { url: 'http://example.com/image.jpg', extension: 'webp' }, // Will be saved as `avatar.webp`
    { url: 'http://example.com/image2.jpg', directory: 'avatars' }, // Will be saved as `avatar.png` in `avatars` directory 
  ],
  { name: 'avatar', extension: 'png' }, // Default options for all images
);

[reslear]

I think arrays are much faster, so I'm suggesting:

const images = [
  { url: 'https://placehold.co/600x400', name: 'myimage'}, 
  { url: 'https://placehold.co/100x200', name: 'fav'}
]

const loads = await imgdl(images)

[fityannugroho]

Well, considering the possibility of use cases where users download images from the same url and want to save it with different attributes (names, extensions, or directory locations), I admit that array is more suitable than objects.

imgdl(
  [
    { url: 'http://example.com/image.jpg', name: 'myavatar' }, // Will be saved as `myavatar.png`
    { url: 'http://example.com/image.jpg', extension: 'webp' }, // Will be saved as `avatar.webp`
    { url: 'http://example.com/image2.jpg', directory: 'avatars' }, // Will be saved as `avatar.png` in `avatars` directory
  ],
  { name: 'avatar', extension: 'png' }, // Default options for all images
);

What do you think @reslear?

[reslear]

LGTM

[fityannugroho]

Has been resolved by PR #20