rbardini / metalsmith-move-up

A Metalsmith plugin for moving the full contents of a directory up one or more levels.

Hi there 👋

I'm Rafael, a frontend developer in the Amsterdam Area. Creator of Carteiro, a popular and highly-rated Android package tracking app in Brazil, as well as several open source projects.

metalsmith-move-up's Issues

Moving just the contents up from directory

I was wondering if there is a way that I can move just the contents one (or more) levels up from a directory.
For example:
| main folder
| – – 1.jpg
| – – subfolder
| – – | – – 2.jpg

In this instance I would like to move 2.jpg into the main folder so it would become:
| main folder
| – – 1.jpg
| – – 2.jpg
| – – subfolder

Is this possible? Thanks

Move travis to rbardini

Right now it tracks to my free travis account, links need to be updated.

Update all licensing and packages refs to rbardini instead of mcdonnelldean

Check if plugin works with metalsmith cli

This has not been checked and may require #2 to be completed first.

• Check if it works as is
• Document changes needed
• Update code to work with metalsmith CLI
• Update tests and docs as applicable

Support more input options for params

Options for metalsmith-move-up are currently supported as such:

moveUp(patternOne, patternTwo, patternN)

Add the ability to support array input:

moveUp([patternOne, patternTwo], patternN, [patternX, patternY])

Input order should be maintained.

Add common patterns / recipies to documentation

The Globbing syntax is not the easiest in the world, it would be nice to add some documentation and / or code samples to show how to do various common tasks with moveup, for instance:

• Flatten the whole destination folder
• Match only a single folder
• Match all files of a single type
• Match all files with the same partial name
• Negate matches
• Match by conditional or filtered pattern

Allow custom minimatch settings

Support custom wide minimatch settings:

• As default settings for all patterns provided
• On a per pattern basis

Improve options / field naming

The naming is confusing in it's current format, the new suggested format is:

• moveUp supports one or more Transforms
• moveUp, by itself does not have any options.
• Transforms can be provided as an collection or an individual Transform
• Transforms have two fields, pattern & upBy
  • pattern: a glob or glob array
  • upBy: the count of directories to move up

These changes need to be reflected in the code, tests and documentation.