Consider removing default mappings

[michaelhogg]

Thank you @mcfarljw for creating this nice plugin!

I encountered an issue regarding the default mappings (date and timestamp). I've set replacePrefix and replaceSuffix to empty strings in my config, and I then found that all occurrences of the words date and timestamp were being replaced in my files – rather unexpected!

A workaround is for the user to set date and timestamp to null in their config:

mappings: {
    date:      null,
    timestamp: null
},
replacePrefix: '',
replaceSuffix: ''

But couldn't the default mappings just be removed from the plugin? Is there a reason why the plugin has these default mappings?

[djelic]

Definitely agree, there shouldn't be any default mappings here.
Workaround if you want avoid replacing date and timestamp:

mappings: {
  date: 'date',
  timestamp: 'timestamp'
},

[mcfarljw]

Interesting, I'd never really considered using it without a prefix and suffix because that seemed a bit risky in terms of unexpected behavior, but I suppose if you're replacing in a 3rd party library then it might not be possible.

I could have it disable the default mappings when the prefix and suffix are set to falsey or empty string values.