WikiDB/Roadmap

From TestWiki
< WikiDB
Revision as of 16:49, 9 August 2021 by HappyDog (Talk | contribs) (Planned features (in progress): syntax)

Jump to: navigation, search

This is an (incomplete) list of features that I plan to add. There are also good ideas from other people scattered around the wiki, which I should really add to this page, but haven't yet.

Note that this page reflects my current development version - if an item is removed from this page due to being implemented, it may not turn up in a public release for a little while.

The bug list has been moved to WikiDB/Bugs. Please report bugs there.

Planned features (in progress)

Table definitions

  • Allow foreign keys to be defined.
  • <data> tags on Table pages should allow the table attribute to be omitted (defaulting to the current page).
  • Allow 'closed' tables (where all data is supplied on the schema page), as a method for implementing Enum fields.

Data types

  • Introduce new class-based method for defining data types (custom and internal) to improve code re-use and to make it easier to add new features.
  • Add 'date' data-type.

Querying back-end

  • Allow JOINS in queries.
  • Add support for boolean NOT operator (AND, OR and XOR are implemented, but NOT is unary and therefore trickier).
  • Add support for LIKE comparisons?
  • Add support for REGEX comparisons?
  • Add support for OFFSET/LIMIT.
  • Add support for field lists and DISTINCT clause.
  • Add support for calculated fields.
  • Add support for custom functions.

Syntax

  • Formalise syntax for referring to identifiers and literals.
  • <repeat> tag:
    • Allow LIMIT argument (or maybe 'range'), possibly with pagination.
    • Add ability to specify field list and limit to DISTINCT rows.
  • <data> tag:
    • Provide a mechanism for 'pass-through' parameters (i.e. parameters that are supplied to the template, but which don't get added to the table). Suggestion is to prefix the name with an exclamation mark. Alternatively, an underscore could be used, as this is already reserved in table definitions, and therefore is not allowed in data tags (though this is not enforced) - may kill two birds with one stone...
    • Allow multi-line field data.

Interface

  • Highlight 'bad' data on the table's data page.
  • Add special page to list all defined data types.
  • 'What links here' should show templates that are included via data tags.

Internals

  • Code Tidying:
    • Add profiling statements.
  • Internationalisation:
    • Allow type names to be translated.
    • Allow type aliases to be translated.
    • Allow tag names to be translated?
    • Allow data to be translated?

Other possible features (speculative)

These are some thoughts on later developments, for further down the line.

Interface

  • Form-based data entry.

Data linking

  • Ability to specify joins between tables.
  • Able to specify relationships between data, e.g. 'is a type of'