📕Documentation Improvements - I need your help🙏

[ahochsteger]

Recently I've put some effort into behind-the-scenes automation to improve the maintenance of examples that enables:

• automatic generation of the example documentation pages
• automatic generation of Jest spec files for unit testing (see *.spec.ts files in sub-folders of this source examples folder)
• automatic generation of end-to-end tests that can be run directly within Google Apps Script (see *.js files in sub-folders of this GAS examples folder).
• selection of examples in the playground

Many other parts of the documentation are already automatically generated as much as possible to make sure it is always up-to-date, like:

• Config Schema
• Enum Types that are used to define possible values for configuration fields
• Actions
• Substitution Placeholder
• Logging Configuration

All this is good, but I feel it still can get better - especially for new users.
That's where I need your help 🙏.
As a user of Gmail Processor there are many ways you can help to improve the documentation like:

• Suggest topics, content or examples you'd expect but did not find
• Describe your use cases to inspire others where Gmail Processor can be of any help
• Contribute documentation or examples by forking gmail-processor
• Anything else that may help users

Thanks in advance for any help!
Andreas

[tepedersen]

The Doc under Exampes/Advanced/Regular Expression might be even better if amended with a quick sentence on how to enable case-insensitive matches.

Spent the longest time trying to get "/.searchword./i" to match, only after I looked through the code for Regexutils did I find out that flags like 'i' should be given as "(?i)searchword" instead, which seems to be a library specific implementation. Now it works great though!

Keep up the great work!

[ahochsteger]

@tepedersen thanks for your great feedback - there's now a note at the RegEx example page.