jamesrwilliams / loquor

An experiment in automatic formatting in Google Sheets using an external API - https://loquor.herokuapp.com

Hi there 👋

I'm a development engineer based in Canada. Currently working with the wonderful team at Points, who enjoys building delightfully fast, easy to use, and engaging digital projects.

https://jamesrwilliams.ca

Socials: Twitter, Instagram, LinkedIn, CodePen

loquor's Issues

Change encoding method

I have this idea to abstract the response encoding method a little during processing as a way to allow support for applying multiple rulesets against a string at once.

Currently, the parser returns [3,13] numerical arrays as results by default. While the AS script works like this I'd like to introduce a middle format to use before the responses are sent. See below:

Step	Input	Encoded
Default to unsafe	<p>Hello World</p>	000000000000000000
Parse layer 1	<p>Hello World</p>	000111111111110000

This output is then encoded into the same numerical array of [3,13] but the output encoded string can be run through multiple rule sets removing possible issues finding overlaps in the numerical arrays.

Add ruleset selection parameter to parse request

We should add a parameter to override what rulesets to be used by the request. Suggested syntax:

Current payload:

{
  "entries" : []
}

Proposed payload:

{
 "options": {
    "rules": ["html, handlebars, twig"]
  }
  "entries" : []
}

HTML Tag Parser: incorrect result for value that start with a tag pair.

HTML Parser unexpected result:

Description	Data
Test Case	<strong>Error:</strong> lorem ipsum.
Expected	111111110000001111111110000000000000
Actual	111111110000001111111111111111111111

Weirdly doesn't happen if the tag is at the end of the string. Or if the whole input starts with an element.

Add parser dialog.

Add UI dialog to allow some configuration changes prior to script runs:

• Select option to change the API version / endpoint (ngrok vs Heroku)
• Input range selection - The input range for the source data to be formatted
• Output range selection - The output range for the formatted section (warning if overwriting input)
• Ruleset selection (Requires API work - see #13)

Handlebars Parser: Unexpected parsing result

handlebarsParser() returns an unexpected result for the following test case:

Description	Data
Test Case	{quantity, plural, one {%lp.currency.name%} other{%lp.currency.name.plural%}}
Expected	11111111111111111111111111111111111111111111111111111111111111111111111111111
Actual	11111111111111111111111111111111111111111110000001111111111111111111111111111

Improve documentation

• Clean up README - Its a bit messy at the moment, extract docs to separate repo/site
• Add docs section - Adding a new validator
• Adding a new test cases
• Google Apps install instructions - (end users)