Very simple storage service for formly json

[chrisekelley]

I originally had planned to use json within the formly templates; unfortunately, the typescript compiler does not accept json (or to be more accurate, does not permit un-escaped '{'). It throws this error:

compiler.es5.js:1689 Uncaught Error: Template parse errors:
Invalid ICU message. Missing '}'. ("

Some discussions on this topic:

• Templates erroring when <code> or <pre> includes any JS/TS "Code" with brackets, tags, etc angular/angular#12916
• ngNonBindable can't handle unescaped { characters angular/angular#11859
• Can't include static json content as part of template html angular/angular#10886

Good news may be that ngNonBindable might be a solution. Until I have tested that out, here is another option, that also could be a start for supporting the use of a GUI editor for forms creation (that saves form data as json).

Service is super-simple - form json is hard-coded in class.

At this point, the default markup format for tangerineBaseCard is yaml. But you have the option to use json:

<tangerine-form-card markup="json" formid="efcard1" #efcard1>
</tangerine-form-card>

There are a couple choices we could make:

• modify service to store json to pouchdb
• save json to a separate file (like the html template) read it upon startup, store in a service, and retrieve as needed.

[chrisekelley]

I also tested out ngNonBindable, that wasn't a solution.

[rjcorwin]

@chrisekelley This is some interesting work. Shall we review for merging or are we thinking we are pivoting and should close?

[chrisekelley]

@rjsteinert It's a little early for this concept; if we push forward with the CKEditor approach we discussed last night, then it's worth revisiting this, refactoring instead to use a new component that follows the pattern you introduced in Tangerine/client-v3/pages/forms/demo.html

[rjcorwin]

@chrisekelley Now that Formly is deprecated, I'll close this PR.