create a built in SSR template engine to use in MVC Projects, should be its own package and should be able to integrated it with a regular Express or other Node app.

anything in {{ ... }} should be evaluated as plain javascript, {{ .. }} must take a call back function that will with return a string or an array of strings, and make use of template strings for data interpolation

example:

// data { title: "FuchsiaJS", items: ["one", "two", "three"]}

// input
<h1>{{ ()=> this.title }}</h1>
<ul>
   {{
      ()=> this.items.map(item => `<li>${item}</li>`
   }}
</ul>

//output

<h1>FuchsiaJS</h1>
<ul>
  <li>one</li>
  <li>two</li>
  <li>three</li>
</ul>

users should be able to create models/entities using jsx/tsx

example

const Episode = () => (
 <Document name='Episode'>
    <Field name='id'>
        <ID />
        </Field>
    <Field name='name'>
        <String />
    </Field>
    <Field name='Length'>
        <Float />
    </Field>
</Document>;
);

const Character = () => (
  <Document name='Character'>
    <Field name='name'>
      <String />
    </Field>
    <Field name='appearsIn' array>
      <Episode />
    </Field>
  </Document>
);

options which can be set currently in the FuchsiaFactory.create() method or in Fuchia.config.json currently do nothing (except databaseOptions) these need to be hooked up.

and include tests.

options:

• urlencoded : should take an object

{
"urlencoded" : {
    "extended": "boolean",
    "inflate": "boolean",
    "limit": "number",
    "parameterLimit": "number",
    "type": "string"
  }
}

• bodyParser: should take an object

{
"bodyParser" : {
    "strict": "boolean",
    "inflate": "boolean",
    "limit": "number",
    "type": "string"
  }
}

• static: should take an object or string

{
"static" : "string"
}



{
"static" : {
    "dotfiles": "string",
    "etag": "boolean",
    "extensions": "array<string>",
    "fallthrough": "string",
    "immutable": "boolean",
    "index" : "string",
    "lastModified" : "boolean",
    "maxAge" : "number",
    "redirect" : "boolean",
  }
}

• caseSenstiveRouting: Boolean
• env: String
• etag: Array
• jsonPCallbackName: String
• jsonEscape: Boolean
• jsonReplacer: String
• jsonSpaces: number
• queryParser: string
• strictRouting: Boolean
• subdomainOffset: number
• trustProxy: string
• views: string
• viewCache: boolean
• viewEngine: string
• xPoweredBy: boolean

at the moment the curried function syntax is a bit odd, i think this functionality needs to be abstracted more in the route components. maybe so the new routes will only receive the request object and the functions return value will be parsed as json by default.

any reponse types needed will need to be wrapped in a specific Response class (eg. HTTPresponse("hello"), FileResponse('index.html'))

should be able to register models to the app where they are then passed into controllers as a parameter,