Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | util.datamapper: Add references with notes | Kim Alvefur | 2021-03-10 | 1 | -0/+14 |
| | |||||
* | util.datamapper: Add Copyright header | Kim Alvefur | 2021-03-10 | 1 | -0/+6 |
| | |||||
* | util.jsonschema: Add copyright-header | Kim Alvefur | 2021-03-10 | 1 | -0/+9 |
| | |||||
* | util.jsonschema: Restructure "type" keyword handling | Kim Alvefur | 2021-03-09 | 1 | -9/+10 |
| | | | | More in line with the other tests | ||||
* | util.jsonschema: Syntax tweak to not upset syntax highlighting | Kim Alvefur | 2021-03-09 | 1 | -2/+2 |
| | | | | | That whole condition stanza was shown as angry red, I think it's something with 'enum' being a key word in Teal. | ||||
* | util.jsonschema: Implement "propertyNames" | Kim Alvefur | 2021-03-09 | 1 | -0/+7 |
| | | | | This is a bit special in Lua as tables are not limited to string keys | ||||
* | util.jsonschema: Restructure handling of "properties" and "additionalProperties" | Kim Alvefur | 2021-03-09 | 1 | -22/+8 |
| | | | | This is a bit cleaner, I think | ||||
* | util.jsonschema: Fix "uniqueItems" prematurely declaring a match | Kim Alvefur | 2021-03-09 | 1 | -1/+0 |
| | |||||
* | util.jsonschema: Implement the "prefixItems" keyword | Kim Alvefur | 2021-03-09 | 1 | -1/+13 |
| | | | | This may have been what got me confused about "items" being an array. | ||||
* | util.jsonschema: Implement the "contains" keyword | Kim Alvefur | 2021-03-09 | 1 | -1/+14 |
| | | | | And apparently I had mistaken this for an array | ||||
* | util.jsonschema: Allow a boolean as schema | Kim Alvefur | 2021-03-09 | 1 | -1/+4 |
| | | | | | | Apparently a schema must be either an object or a boolean. Not sure where I got this string shortcut from, but I think I will keep it as it is very convenient. | ||||
* | util.jsonschema: Correct "items" keyword | Kim Alvefur | 2021-03-09 | 1 | -13/+5 |
| | | | | | | Upon re-reading the JSON Schema spec, I found that 'items' wasn't a union of an array of schemas or a single schema, not sure where I got that from. | ||||
* | util.datamapper: Add support for mapping of elements where only one ↵ | Kim Alvefur | 2021-03-07 | 2 | -0/+35 |
| | | | | | | | attribute matters E.g. <feature var='foo'/> in XEP-0030 and some other simple specifications. | ||||
* | util.datamapper: Add logic for "boolean" tags here the presence means true | Kim Alvefur | 2021-03-07 | 1 | -3/+9 |
| | |||||
* | util.datamapper: Invent extension for using tag name as value | Kim Alvefur | 2021-03-06 | 2 | -2/+16 |
| | | | | | Useful for certain enum-like uses where the element name is the relevant information, e.g. chat states. | ||||
* | util.datamapper: Add 'unparse' for turning tables into XML | Kim Alvefur | 2021-03-07 | 1 | -1/+102 |
| | |||||
* | util.datamapper: Library for extracting data from stanzas | Kim Alvefur | 2021-03-07 | 1 | -0/+100 |
| | | | | Based on the XML support in the OpenAPI specification. | ||||
* | util.jsonschema: Library for JSON Schema validation | Kim Alvefur | 2021-03-06 | 1 | -0/+327 |
| | |||||
* | util: Add Teal interface definition files | Kim Alvefur | 2021-03-09 | 24 | -0/+489 |
Enables writing code in Teal that is aware of the interfaces and function prototypes in these other utils. Could also be used to do type checks on Lua sources, but this tends to have a lot of noise. |