Remove filename requirement

Follow

Pro

• February 08, 2018 12:23

I don't think it should be required to add a filename to a snippet. I mean like snippets can usually be used in any file, and only sometimes I use a real filename when a snippet should go in a specific file. I usually just fill in the filename with anyfile.php.

3

• 

  Wesley Smith

  • June 14, 2018 00:59

  I feel like this is more complex than it seems due to the various integrations. For example, if your account is linked to your github account, creating a snippet in cacher will also create a gist in github and each file you add to the snippet, that file is also saved to the gist. This kind of syncing, and the ability to turn it on or off, or change integrations, adds a lot of complexity that is solved by requiring a filename.

   

  Maybe a compromise could be to have a setting like "Autofill filenames" or similar and if this is selected, it automatically fills in a randomly generated filename when files are added.

   

   

  2

  Comment actions Permalink
• 

  Eliseu

  • June 18, 2018 04:50
  • Edited

  I agree with Wesley Smith that it could be harder than it seems. A default name like `file{1...N}.{extension}` should do it, no?

  0

  Comment actions Permalink

Please sign in to leave a comment.