| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | util.datamapper: Fix to skip parsing wrapped arrays that aren't there | Kim Alvefur | 2021-03-22 | 1 | -2/+0 |
| | | | | | Turns out the unreachable error is reachable :D | ||||
| * | util.datamapper: Complete array building support | Kim Alvefur | 2021-03-20 | 1 | -12/+3 |
| | | |||||
| * | util.datamapper: Factor out handling of object properties for array reuse | Kim Alvefur | 2021-03-20 | 1 | -79/+82 |
| | | |||||
| * | util.datamapper: Finally implement support for parsing arrays | Kim Alvefur | 2021-03-20 | 1 | -13/+9 |
| | | |||||
| * | util.datamapper: Factor out extraction of the XML part to use | Kim Alvefur | 2021-03-20 | 1 | -40/+42 |
| | | | | | | | | | So extract_value() takes an XML tag and details about which part we're interested in and returns that. Factoring this out will help with array implementation since this will be common behavior. | ||||
| * | util.datamapper: Only get element name if there's an element | Kim Alvefur | 2021-03-19 | 1 | -1/+3 |
| | | | | | Fixes error due to attempting to index a nil value | ||||
| * | util.datamapper: Fix arrays nesting one level too deep | Kim Alvefur | 2021-03-19 | 1 | -9/+9 |
| | | |||||
| * | util.datamapper: Deal with type name changes in util.jsonschema | Kim Alvefur | 2021-03-19 | 1 | -1/+1 |
| | | |||||
| * | util.datamapper: Limited support for unparsing simple arrays of strings | Kim Alvefur | 2021-03-18 | 1 | -11/+41 |
| | | |||||
| * | util.datamapper: Add initial support for parsing arrays | Kim Alvefur | 2021-03-18 | 1 | -9/+47 |
| | | |||||
| * | util.datamapper: Factor out common schema unpacking | Kim Alvefur | 2021-03-14 | 1 | -80/+53 |
| | | | | | | This code extracts the bits from the schema that determines how the data is to be mapped to/from XML. | ||||
| * | util.datamapper: Separate extraction of xml from coercion to target type | Kim Alvefur | 2021-03-14 | 1 | -34/+28 |
| | | | | | | | Now it gets the text, attribute or name first, then turns it into whatever the schema wants. This should be easier to further factor out into preparation for array support. | ||||
| * | util.datamapper: Use enum instead of mutually exclusive booleans | Kim Alvefur | 2021-03-14 | 1 | -20/+20 |
| | | | | | Cleaner and rules out invalid combinations. | ||||
| * | util.datamapper: Enumerated elements | Kim Alvefur | 2021-03-12 | 1 | -1/+20 |
| | | | | | E.g. error conditions or chat states. | ||||
| * | util.datamapper: Add references with notes | Kim Alvefur | 2021-03-10 | 1 | -0/+3 |
| | | |||||
| * | util.datamapper: Add support for mapping of elements where only one ↵ | Kim Alvefur | 2021-03-07 | 1 | -0/+34 |
| | | | | | | | | 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 | 1 | -2/+15 |
| | | | | | | 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/+96 |
| Based on the XML support in the OpenAPI specification. | |||||
 |
index : prosody.git | |
| unofficial mirror of the prosody mercurial project |
| aboutsummaryrefslogtreecommitdiffstats |