Kyle Jessup
Kyle Jessup
The following works: {{% handler:FAHandler}}{{! This is the moustache template file }}{"resultSets":[{{#resultSets}}{"time":"{{time}}","lat":{{lat}},"long":{{long}} }{{^last}},{{/last}}{{/resultSets}}]} While this causes parsing problems: {{% handler:FAHandler}}{{! }}{"resultSets":[{{#resultSets}}{"time":"{{time}}","lat":{{lat}},"long":{{long}} }{{^last}},{{/last}}{{/resultSets}}]} The system skips the closing empty comment delimiters.
The static file handler which setting the HTTPServer.documentRoot property adds does not indicate "allowResponseFilters" as true. This can conflict with the content compression filter. The static file handler should have...
``` struct Foo { let d: Double? } …where(\Foo.d < 5.0)… ``` The above gives a compilation error. Work around is: ``` …where(\Foo.d! < 5.0)… ``` While Swift won't technically...
At the least, cascade deletes should be supported.
E.g. …where( (\Type.anInt & 0x01) != 0)… ~ & | ^ >>
Self joins work but there is no way to differentiate between the two same-but-different tables in a `where` clause.
If it's possible to determine a default value for a type's property, it could possibly be used in the table `create`. If not, user could indicate defaults for these columns...
`GROUP BY` or `HAVING` How would these look? LINQ is something like this: from p in persons group p.car by p.PersonId into g select new { PersonId = g.Key, Cars...
JWT base64url requires padding '=' chars to be stripped, but some other uses need the '=' to be preserved. An encoding should be added which leaves the = intact, replacing...
Some of the headers which were added more recently have bad case here. https://github.com/PerfectlySoft/Perfect-HTTP/blob/master/Sources/PerfectHTTP/HTTPHeaders.swift#L302 Should be all lower case.