Handle empty JSON

�� Automatic code style fixes

�� Automatic code style fixes

Rename internal schemas to "internal"

Manual code style adjustments

PHP code sniffer autofixes

Eliminate warnings in PHP 8

refactoring names

To avoid confusion with the Lookup type, the three different ways of
accessing a schema have now the following names:

* page data - for revisioned struct data attached to a page
*

refactoring names

To avoid confusion with the Lookup type, the three different ways of
accessing a schema have now the following names:

* page data - for revisioned struct data attached to a page
* serial data - for an unrevisioned list of struct data attached to a
page
* global data - for an unrevisioned list of struct data not attached to
any page (formaly known as lookup schema)

The editor mechanism used for serial and global data is now called
AggregationEditor

Some reference to lookup schemas is still in the bureaucracy support
part.

show more ...

Introduce new factory methods for data access and deprecate old ones

Add wrapper function for json_decode()

Automatic coding style fixes

Pass current time instead of 0 to fetch data of latest page revision

Remove redundant serial code

There is actually very little need to split the handling of lookup (not page specific) and serial (page bound) data, because row ids are globally unique and never shared

Remove redundant serial code

There is actually very little need to split the handling of lookup (not page specific) and serial (page bound) data, because row ids are globally unique and never shared between those two types.

show more ...

Some fixme cleanups

Rudimentary handling of serial data

Serial data is bound to a page but does not affect versioning

Start unifying schema types

Schemas per se are type agnostic, isLookup property is removed. Data is stored and accessed differently based on how it is entered and retrieved.

The crucial change is i

Start unifying schema types

Schemas per se are type agnostic, isLookup property is removed. Data is stored and accessed differently based on how it is entered and retrieved.

The crucial change is introduction of the composite key of pid and rid. Previous page data utilizes rid = 0 to differentiate itself. Other types, notably lookup, have autoincrementing rid.

Database migration is not implemented yet.

show more ...

Merge pull request #433 from glensc/api-minor-edit

remote: allow making minor edits

�� Fix saved lookup row not being displayed

This fixes a bug that was introduced in ff2afc7c7bdf9f04b6bc2917af42ff865757c54d

When saving the lookup we need the id of the row we just saved to create

�� Fix saved lookup row not being displayed

This fixes a bug that was introduced in ff2afc7c7bdf9f04b6bc2917af42ff865757c54d

When saving the lookup we need the id of the row we just saved to create
the response to the original ajax request.

Closes #398

show more ...

remote: allow making minor edits

refactor: Move saving of lookup row to helper method

This should make saving lookup data easier, both for tests and external plugins

made Assignments singleton. fixes #163

more Validator refactoring

inline editing for lookups works now

Additionally only the edited field not the wohle row is validated now.

renamed SchemaData and SchemaLookupData

This is to reflect that they no longer inherit from Schema

refactor SchemaData into AccessTable with factory

first part of the refactoring for the SchemaData and SchemaLookupData
classes. Both now inherit from AccessTable which provides common methods
and t

refactor SchemaData into AccessTable with factory

first part of the refactoring for the SchemaData and SchemaLookupData
classes. Both now inherit from AccessTable which provides common methods
and two factory methods to automatically create the correct class
depending on the schema.

Both classes no longer inherit from Schema. Instead they contain a
Schema as a member variable. This makes it possible to initialize them
with an existing schema (which is required for the factory methods).

The flow is now like this:

1: init a schema (read info from the database)
2: look at the schema to figure out if it's a lookup or not
3: initialize the right Data object with the schema

show more ...