aboutsummaryrefslogtreecommitdiffstats
path: root/teal-src
Commit message (Collapse)AuthorAgeFilesLines
* teal-src/README: Words on Compiling to LuaKim Alvefur2023-03-281-0/+17
|
* teal-src/README: Tweak markdown syntaxKim Alvefur2023-03-281-1/+3
|
* teal-src: Add a README with a few pointers to get startedKim Alvefur2023-03-281-0/+29
|
* teal-src: Add keyval+ store typeMatthew Wild2023-03-281-0/+1
|
* util.jsonschema: Reorder type definition by specification, sectionKim Alvefur2023-03-261-14/+37
| | | | Also some comment headers and missing properties
* util.jsonschema: Implement 'dependentSchemas'Kim Alvefur2023-03-261-0/+9
| | | | | If this object key exists then this schema must validate against the current object. Seems useful.
* util.jsonschema: Implement 'dependentRequired'Kim Alvefur2023-03-261-0/+12
| | | | If this field exists, then these fields must also exist.
* teal: Move into prosody namespaceKim Alvefur2023-03-2360-19/+19
|
* util.ip: Add Teal interface descriptionKim Alvefur2023-03-141-0/+20
|
* util.jwt: Import definition of key from util.cryptoKim Alvefur2023-03-101-4/+2
| | | | Turns out we had a definition of that already
* util.jwt: Fixup argument and type orderKim Alvefur2023-03-101-1/+1
|
* util.jwt: Document interface as Teal definition fileKim Alvefur2023-03-101-0/+40
|
* core.usermanager: Add methods for enabling and disabling usersKim Alvefur2023-02-231-0/+3
| | | | Calling into the auth module, where available.
* core.usermanager: Add Teal description fileKim Alvefur2023-02-231-0/+43
|
* MUC: Add Occupant API methods to Teal specKim Alvefur2023-02-201-0/+6
|
* MUC: Add Teal description of muc.lib functionsKim Alvefur2023-02-201-0/+9
|
* MUC: Start on a Teal description of MUC roomsKim Alvefur2023-02-201-0/+163
| | | | Started as part of a documentation project for the MUC API
* util.mathcompat: Module to ease reuse of math.type()Kim Alvefur2022-10-203-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 Alvefur2022-10-191-4/+0
|
* util.stanza: Add new methods to Teal interface specificationKim Alvefur2022-10-171-0/+5
| | | | | | | at_top: 21217f7e82b9 get_child_with_attr: 39164ea2ab9e get_child_attr: e8934ce6ea0f add_error: 5f182bccf33f
* util.crypto: Add Teal type specificationKim Alvefur2022-06-301-0/+29
|
* util.roles: Add Teal interface declarationKim Alvefur2022-08-121-0/+32
|
* teal-src: update module.d.tl with new access control methodsMatthew Wild2022-06-151-0/+5
|
* util.datetime: Update Teal interface descriptionKim Alvefur2022-08-171-7/+5
| | | | Integers were required before, now any number should work.
* util.signal: Fix name conflict in Teal interface declarationKim Alvefur2022-08-101-4/+4
|
* util.error: Use avoid name conflict in Teal interface declarationKim Alvefur2022-08-101-8/+8
| | | | Naming things ... Thing or thing_t?
* util.uuid: Fix syntax of Teal interface declaration fileKim Alvefur2022-08-101-1/+1
|
* util.timer: Add Teal interface descriptionKim Alvefur2022-07-241-0/+8
|
* util.termcolours: Add Teal interface descriptionKim Alvefur2022-07-241-0/+7
|
* util.queue: Add Teal interface descriptionKim Alvefur2022-07-241-0/+21
|
* util.logger: Add Teal interface descriptionKim Alvefur2022-07-241-0/+18
|
* util.bitcompat: Add Teal type specificationKim Alvefur2022-06-301-0/+8
|
* util.struct: Add Teal interface description fileKim Alvefur2022-06-151-0/+6
|
* util.table: Add move() to Teal interface description fileKim Alvefur2022-06-151-0/+1
|
* util.set: Add teal type declaration fileKim Alvefur2022-02-161-0/+21
|
* util.serialization: Add Teal type specificationKim Alvefur2021-12-011-0/+33
|
* util.dataforms: Add missing :data() to Teal definitionKim Alvefur2021-11-151-0/+1
|
* util.dataforms: Restructure Teal definition fileKim Alvefur2021-11-151-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 definitionKim Alvefur2021-11-101-0/+28
|
* util.promise: Add Teal interface specification fileKim Alvefur2022-07-242-3/+23
|
* teal: add stub util.array teal defsKim Alvefur2022-07-241-0/+9
|
* net.server: Add teal description fileKim Alvefur2022-07-241-0/+65
|
* net.http: Add teal description filesKim Alvefur2022-07-246-0/+190
|
* util.human.units: Specify enum argument to format()Kim Alvefur2021-07-051-1/+4
|
* core.storagemanager: Convert old Typed Lua description file into TealKim Alvefur2021-03-241-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 a0ff5c438e9dKim Alvefur2022-08-101-0/+2
|
* Merge 0.12->trunkKim Alvefur2022-07-082-159/+183
|\
| * util.datamapper: Improve handling of schemas with non-obvious "type"Kim Alvefur2022-07-081-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" fieldKim Alvefur2022-07-081-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 bindingsKim Alvefur2020-09-101-0/+4
| |
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-28 21:39:28 +0000