chrisdmacrae / front-matter-manipulator

A utility for parsing and manipulating documents with Front Matter

Hi there 👋

Hi there, I'm Chris. I'm a designer, full stack developer, writer, father and husband.

I work at Careguide, where I am the lead engineer, leading a team of 8 developers and 2 designers, helping care providers connect with families to bring care to the world.

---

Background

I've been working in tech since 2013. I started my career as a designer, graduating with an associates diploma in interdiscplinary design.

I spent two years working in marketing as a brand designer. Then I spent two years as a product designer working exclusively on mobile apps. After that I spent roughly two years running my own business offering branding, search engine optimization, and inbound marketing services, which I then closed shop on and handed off all of my clients.

I've spent the last four years working as a fullstack developer. I've gotten to work as a team lead, technical project manager, and scrum master (for better or for worse).

Location

I live and work from beautiful, seaside, Morell, Prince Edward Island in Eastern Canada.

Links

• Twitter, @chrisdmacrae
• Github, @chrisdmacrae
• LinkedIn: @chrisdmacrae

front-matter-manipulator's Issues

Convert to fully async, promise-based

Problem we're trying to solve

Currently the commands are written partially synchronous, which means the I/O can be blocked when reading many files or updating many files.

Moving to promise-based async will allow the commands to run much faster.

General

• Update update to be async
• Update rename to be async
• Update valuesto be async
• Update fields to be async

Specific

• Update all array functions to be async
• Update all readFileSync and writeFileSync to be async
• Update all glob actions to be async

Add drop command

Problem's we're trying to solve

In some cases you may have a bunch of extra fields that you no longer need, being able to batch remove them from many files is ideal.

Currently, either the CMS you use must do this, you must do it by hand, or by writing a script.

• Allow specifying many fields to be dropped from the globbed files
• Ensure that a confirmation is used by default, as this destructive behaviour is not easily undone without version control

Add a merge command

Problem's we're trying to solve

In some cases, you may have many fields that are very similar or are used for the same purpose, and want to consolidate these to have leaner FMTs.

This currently requires a lot of tedious, manual work. Having a utility that finds all possible values for each key, and allows you to merge them / pick a preferred value for a single (or new key) would be ideal for site migration and updating.

• Add ability to query the values of a file by key
• Allow the specification of the replacement key
• Prompt the user for the correct value
• Allow the user to optionally specify a "winner cascade", where values don't need to be confirmed, but are used in order found. (E.g, --by-fields description,summary,excerpt)

Add ability to add new data set

It would really be great if update was able to add a new data key/value pair when passing an in-existing key as argument.

The current behaviour when doing the above is a successfully updated list of items. Yet the data set is not added.