Remove unnecessary <div>

Apparently a <p class="hint"> is enough after all and the surrounding
diff is redundant.

SPR-899

Wrap the hint in the inline editor in a p tag

For it to be read correctly by screen readers and for better styling,
wrap the hint in the inline-editor in a <p>-tag.

SPR-899

Version upped

Fix a `let` that we missed for IE10 compatibility

IE10 does not understand `let` and `const`, so we still have to use var

Version upped

removed unused files

Version upped

introduce event to allow plugins to parse additional configs

Version upped

Do not break migrations of other plugins

SPR-850

Fix typo

At least it was consistent...

Throw on missing column

This happens if the user explicitly enters a column that does not exist in the
schema. This error was previously silently ignored.

This adjustment notifies the user that the

Throw on missing column

This happens if the user explicitly enters a column that does not exist in the
schema. This error was previously silently ignored.

This adjustment notifies the user that there is an error.

show more ...

Add compareValue() abstract base type & lookup

This fixes a bug, that caused the $STRUCT.table.field$ filter syntax to
be broken for lookup fields. Struct was comparing the row-id of the
argument-c

Add compareValue() abstract base type & lookup

This fixes a bug, that caused the $STRUCT.table.field$ filter syntax to
be broken for lookup fields. Struct was comparing the row-id of the
argument-column to the raw value of the referenced column at the
filtered lookup.

There were multiple options to fix this bug:
1. Add a new function to the AbstractBaseType() that return raw value by
default (this is the approach implemented by this commit)
2. Add a function to the lookup type only and use introspection to call
it if it exists.
3. Do not compare the values in the referenced columns, but compare only
the row-ids

The problem with approach 3: It is not possible to compare such
lookup-column to any other column except lookups and this is not what we
want.
Approaches 1 and 2 have different trade-offs on where additional
code/complexity is created. I decided for approach 1 because it is the
cleaner overall approach and we might want to use this functionality for future
types as well.

SPR-875

show more ...

Use labels as keys for getData array of Values

This makes accessing the value of a specific column easier, since
otherwise we would have to loop through the array and call getLabel for
every column.

Use labels as keys for getData array of Values

This makes accessing the value of a specific column easier, since
otherwise we would have to loop through the array and call getLabel for
every column.

Tests have been adjusted.

show more ...

Version upped

Move edited multiwrap out of .newtemplate container

Fixes issue #276

Show translated label in entry-forms as well

refactor: use trait to reduce duplicate code

tests: schema-name should match schema2.struct.json

feat: Show translatable schema names on pages

SPR-841 #45

Render only in show but parse in every mode

It might happen that a page is parsed in other modes than show and the
result might be cached, so it should contain the struct instruction.
However we onl

Render only in show but parse in every mode

It might happen that a page is parsed in other modes than show and the
result might be cached, so it should contain the struct instruction.
However we only want to display the output when viewing a page and not
for example in a edit session.

show more ...

fix: Add struct instruction to all pages

There was a bug when using struct on a page together with log and
include plugin. The unintended behavior: the struct data would not be
shown after the first

fix: Add struct instruction to all pages

There was a bug when using struct on a page together with log and
include plugin. The unintended behavior: the struct data would not be
shown after the first heading of the page, but after the first include
if present, or not at all.
The reason for this behavior was that the log-plugin caused the $ID == $this->lastread
check to fail.

This solution removes this check altogether and leaves it to the
renderer to decide if the data should be rendered or not.

SPR-634

show more ...

tests: add explanation to failing asserts

tests: add tests output instructions

SPR-634

added admin icon