search

VerdeCircle / strapi-provider-upload-cloudinary-folderoptions

an extension of the strapi-provider-upload-cloudinary that allows for a default_folder option in the config as well as using the file name to define folder structure.
https://www.npmjs.com/package/strapi-provider-upload-cloudinary-folderoptions
Other
12 stars 3 forks source link

why a distinct repository ? #3

Open petitkriket opened 2 years ago

petitkriket commented 2 years ago

Hi !

Thank you for your work !

I was wondering, why a single feature would need a distinct project ?

Using the main package (strapi-provider-upload-cloudinary) like so does exactly the same thing, is additional value to using this package ?

module.exports = ({ env }) => ({
  upload: {
    provider: 'cloudinary',
    providerOptions: {
      cloud_name: env('CLOUDINARY_NAME'),
      api_key: env('CLOUDINARY_KEY'),
      api_secret: env('CLOUDINARY_SECRET'),
    },
    actionOptions: {
      upload: {
        folder: env('NODE_ENV'),
      },
      delete: {},
    },
  },
});

Cheers

Jaredude commented 2 years ago

I'm not sure I understand the question. Adding a single feature would branch from from the original repo as a new repo. If someone wants to make this part of the main repo they can make the PR. By having a distinct project, additional features like this (being able to upload to a folder) can be put in place without having to wait for a PR to the original project to be approved.