Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | teal-src/README: Tweak markdown syntax | Kim Alvefur | 2023-03-28 | 1 | -1/+3 |
| | |||||
* | teal-src: Add a README with a few pointers to get started | Kim Alvefur | 2023-03-28 | 1 | -0/+29 |
| | |||||
* | teal-src: Add keyval+ store type | Matthew Wild | 2023-03-28 | 1 | -0/+1 |
| | |||||
* | util.jsonschema: Reorder type definition by specification, section | Kim Alvefur | 2023-03-26 | 1 | -14/+37 |
| | | | | Also some comment headers and missing properties | ||||
* | util.jsonschema: Implement 'dependentSchemas' | Kim Alvefur | 2023-03-26 | 1 | -0/+9 |
| | | | | | If this object key exists then this schema must validate against the current object. Seems useful. | ||||
* | util.jsonschema: Implement 'dependentRequired' | Kim Alvefur | 2023-03-26 | 1 | -0/+12 |
| | | | | If this field exists, then these fields must also exist. | ||||
* | teal: Move into prosody namespace | Kim Alvefur | 2023-03-23 | 60 | -19/+19 |
| | |||||
* | util.ip: Add Teal interface description | Kim Alvefur | 2023-03-14 | 1 | -0/+20 |
| | |||||
* | util.jwt: Import definition of key from util.crypto | Kim Alvefur | 2023-03-10 | 1 | -4/+2 |
| | | | | Turns out we had a definition of that already | ||||
* | util.jwt: Fixup argument and type order | Kim Alvefur | 2023-03-10 | 1 | -1/+1 |
| | |||||
* | util.jwt: Document interface as Teal definition file | Kim Alvefur | 2023-03-10 | 1 | -0/+40 |
| | |||||
* | core.usermanager: Add methods for enabling and disabling users | Kim Alvefur | 2023-02-23 | 1 | -0/+3 |
| | | | | Calling into the auth module, where available. | ||||
* | core.usermanager: Add Teal description file | Kim Alvefur | 2023-02-23 | 1 | -0/+43 |
| | |||||
* | MUC: Add Occupant API methods to Teal spec | Kim Alvefur | 2023-02-20 | 1 | -0/+6 |
| | |||||
* | MUC: Add Teal description of muc.lib functions | Kim Alvefur | 2023-02-20 | 1 | -0/+9 |
| | |||||
* | MUC: Start on a Teal description of MUC rooms | Kim Alvefur | 2023-02-20 | 1 | -0/+163 |
| | | | | Started as part of a documentation project for the MUC API | ||||
* | util.mathcompat: Module to ease reuse of math.type() | Kim Alvefur | 2022-10-20 | 3 | -0/+19 |
| | | | | | Mostly to ensure it is available during tests, as util.startup is not invoked there | ||||
* | util.datamapper: Remove leftover debug assert (Only Teal, not included in build) | Kim Alvefur | 2022-10-19 | 1 | -4/+0 |
| | |||||
* | util.stanza: Add new methods to Teal interface specification | Kim Alvefur | 2022-10-17 | 1 | -0/+5 |
| | | | | | | | at_top: 21217f7e82b9 get_child_with_attr: 39164ea2ab9e get_child_attr: e8934ce6ea0f add_error: 5f182bccf33f | ||||
* | util.crypto: Add Teal type specification | Kim Alvefur | 2022-06-30 | 1 | -0/+29 |
| | |||||
* | util.roles: Add Teal interface declaration | Kim Alvefur | 2022-08-12 | 1 | -0/+32 |
| | |||||
* | teal-src: update module.d.tl with new access control methods | Matthew Wild | 2022-06-15 | 1 | -0/+5 |
| | |||||
* | util.datetime: Update Teal interface description | Kim Alvefur | 2022-08-17 | 1 | -7/+5 |
| | | | | Integers were required before, now any number should work. | ||||
* | util.signal: Fix name conflict in Teal interface declaration | Kim Alvefur | 2022-08-10 | 1 | -4/+4 |
| | |||||
* | util.error: Use avoid name conflict in Teal interface declaration | Kim Alvefur | 2022-08-10 | 1 | -8/+8 |
| | | | | Naming things ... Thing or thing_t? | ||||
* | util.uuid: Fix syntax of Teal interface declaration file | Kim Alvefur | 2022-08-10 | 1 | -1/+1 |
| | |||||
* | util.timer: Add Teal interface description | Kim Alvefur | 2022-07-24 | 1 | -0/+8 |
| | |||||
* | util.termcolours: Add Teal interface description | Kim Alvefur | 2022-07-24 | 1 | -0/+7 |
| | |||||
* | util.queue: Add Teal interface description | Kim Alvefur | 2022-07-24 | 1 | -0/+21 |
| | |||||
* | util.logger: Add Teal interface description | Kim Alvefur | 2022-07-24 | 1 | -0/+18 |
| | |||||
* | util.bitcompat: Add Teal type specification | Kim Alvefur | 2022-06-30 | 1 | -0/+8 |
| | |||||
* | util.struct: Add Teal interface description file | Kim Alvefur | 2022-06-15 | 1 | -0/+6 |
| | |||||
* | util.table: Add move() to Teal interface description file | Kim Alvefur | 2022-06-15 | 1 | -0/+1 |
| | |||||
* | util.set: Add teal type declaration file | Kim Alvefur | 2022-02-16 | 1 | -0/+21 |
| | |||||
* | util.serialization: Add Teal type specification | Kim Alvefur | 2021-12-01 | 1 | -0/+33 |
| | |||||
* | util.dataforms: Add missing :data() to Teal definition | Kim Alvefur | 2021-11-15 | 1 | -0/+1 |
| | |||||
* | util.dataforms: Restructure Teal definition file | Kim Alvefur | 2021-11-15 | 1 | -45/+46 |
| | | | | | The PR has been merged and there's no reason not to have nested records and other definitions. | ||||
* | util.human.io: Add Teal interface definition | Kim Alvefur | 2021-11-10 | 1 | -0/+28 |
| | |||||
* | util.promise: Add Teal interface specification file | Kim Alvefur | 2022-07-24 | 2 | -3/+23 |
| | |||||
* | teal: add stub util.array teal defs | Kim Alvefur | 2022-07-24 | 1 | -0/+9 |
| | |||||
* | net.server: Add teal description file | Kim Alvefur | 2022-07-24 | 1 | -0/+65 |
| | |||||
* | net.http: Add teal description files | Kim Alvefur | 2022-07-24 | 6 | -0/+190 |
| | |||||
* | util.human.units: Specify enum argument to format() | Kim Alvefur | 2021-07-05 | 1 | -1/+4 |
| | |||||
* | core.storagemanager: Convert old Typed Lua description file into Teal | Kim Alvefur | 2021-03-24 | 1 | -0/+74 |
| | | | | | | | | Still only a type definition. Typed Lua is no longer maintained. Teal is currently an active project. | ||||
* | util.hex: Update Teal spec for function rename in a0ff5c438e9d | Kim Alvefur | 2022-08-10 | 1 | -0/+2 |
| | |||||
* | Merge 0.12->trunk | Kim Alvefur | 2022-07-08 | 2 | -159/+183 |
|\ | |||||
| * | util.datamapper: Improve handling of schemas with non-obvious "type" | Kim Alvefur | 2022-07-08 | 1 | -12/+31 |
| | | | | | | | | | | | | | | | | | | | | | | | | The JSON Schema specification says that schemas are objects or booleans, and that the 'type' property is optional and can be an array. This module previously allowed bare type names as schemas and did not really handle booleans. It now handles missing 'type' properties and boolean 'true' as a schema. Objects and arrays are guessed based on the presence of 'properties' or 'items' field. | ||||
| * | util.jsonschema: Fix validation to not assume presence of "type" field | Kim Alvefur | 2022-07-08 | 1 | -147/+152 |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | MattJ reported a curious issue where validation did not work as expected. Primarily that the "type" field was expected to be mandatory, and thus leaving it out would result in no checks being performed. This was likely caused by misreading during initial development. Spent some time testing against https://github.com/json-schema-org/JSON-Schema-Test-Suite.git and discovered a multitude of issues, far too many to bother splitting into separate commits. More than half of them fail. Many because of features not implemented, which have been marked NYI. For example, some require deep comparisons e.g. when objects or arrays are present in enums fields. Some because of quirks with how Lua differs from JavaScript, e.g. no distinct array or object types. Tests involving fractional floating point numbers. We're definitely not going to follow references to remote resources. Or deal with UTF-16 sillyness. One test asserted that 1.0 is an integer, where Lua 5.3+ will disagree. | ||||
* | | util.hashes: Add SHA3 bindings | Kim Alvefur | 2020-09-10 | 1 | -0/+4 |
| | | |||||
* | | util.hashes: Bind BLAKE2 algoritms supported by OpenSSL | Kim Alvefur | 2020-09-10 | 1 | -0/+2 |
| | |