simonuwe/oracle-apex-json-region

An Oracle-APEX-plugin that provides for each property of a JSON-schema an input field to support an easy way to display and edit a JSON item

oracle-apex-json-region's Issues

configurable labels

Currently labels are derived from property-names.

implement optional assignment of labels to properties.

identifiers in JSON data/schema must be enclosed by "

The ORACLE check "IS JSON" classifies more JSON variants as valid than the javascript JSON.parse.
The main issue is that identifiers must be enclosed by " for Javascripts JSON.parse, but in Oracles IS JSON the enclosing by " is optional.

Workarround: Use only " enclosed identifiers in JSON-schema/data or use CHECK-constraint
IS JSON(STRICT).

Oracle:

SQL> select '{a: 1}' is json "is json" from dual;

   is json
----------
         1
SQL> select '{a: 1}' is json(strict) "is json" from dual;

   is json
----------
         0
SQL> select '{"a": 1}' is json "is json" from dual;

   is json
----------
         1

Javascript:

JSON.parse('{a:1}');
Uncaught SyntaxError: Unexpected token a in JSON at position 1
JSON.parse('{"a":1}');
{ a: 1 }

support of "additionalProperties"

When "additionalProperties" is defined and != false, properties not mentioned in the object are kept when updating the data.

This schema-property could be overwritten by JSON-region-configuration Keep attributes when not set or is false.

No warning on data change and close

When only data in JSON is changed, there is no warning when page is left without submit.

Language mismatch in errormessages

Some Error messages are always in German (EMail, Website)

enum could not be saved, returns invalid

field validation always returns "xxx is invalid"

switch always "false" when readonly

the switch-widget shows false when json-region is readonly.

Support PWA

Make plugin working with PWA

Date/date-time picker with minimum/maximum

Support of "minimum", "maximum" for "date" and "date-time"-picker

Recursive $ref does not work in JSON-schema

Support APEX-23.2 combobox

Support APEX-23.2 combobox for multiple selection.

Export/Import of application causes inline-errormessages to disapear

The inline error-messages are not shown inside plugin when application is exported and imported again.

Support of JSON-schema keyword const

To always fill a property with the same value.

Example:

{
---
  properties": {
    "source": {
      "const": "via APEX-application";
    }
...
  }
...
}

Support of "dependentRequired"

Support den "dependentRequired" attribute of json-schema.

"dependentRequired": {
    "credit_card": ["billing_address"]
  }

This means: when item credit_card is filled then billing address must be filled too.

Support for different themes

Currently theming only works correct with universal-theme 42.

Remove all null properties from JSON

An option to remove null properties from objects like

{
  "a1": "t1",
  "a2": null,
  "a3": "t3"
}

is reduced to

{
  "a1": "t1",
  "a3": "t3"
}

"undefined" error with empty nested object

Header for subobjects

If JSON contains subobjects with similar content/fields a header make usage more userfriendly

[Lastname] [Firstname]
Company Address
[ZIP] [City]

Postal Address
[Zip] [City]

widget.NumberField not loaded when debug is enabled

when debug is enabled widget.numberFields.js is not loaded, so validation of numberFields does not work.

When setting debuglevel to no debug it works fine,

This in an APEX-Bug.

display of JSON in lists

• Configuration
• Format of list entry
• Layout?

Help texts lost during backport to APEX-22.1

The help texts for the configuration of the json-region are missing.

css lost for APEX-22.1

APEX-22.1 does not automatically minimize .css files. but the File-include uses die json-region#MIN#.css.

Works fine as long you are in Debug mode (here the non-min-files are used).

Solution: remove the #MIN# (file is only 3 lines).

Option to keep attributes not specified in JSON-schema

An boolean config option to keep other parts of the JSON while updating.

• Overwrite parts of the JSON not mentioned in JSON-schema
• Keep parts of the JSON not mentioned in JSON-schema

array of properties

support of arrays like

{
  "type":"object",
  "properties": {
    "lastname": {"type": "string"},
    "firstname": {"type: "string"},
    "emails": {"type": "array",
      "maxItems": 3,
      "items": { "type": "object",
         "properties": {
           "email": {"type": "string"},
           "type":  {"type": "string"}
      }
    .....
   }
}

Compatibility broken

Plugin/Demo only work with APEX-23.1

Support of string formats email and uri

missing part in JSON-schema description cause javascript errors

When attributes "type" or "properties" are missing in the JSON-schema description the browser throws errors on its console.

picker for date/date-time allows invalid entires

Manually editing the dat/date-time field allows entring invalid values.

Support of $defs

Support $defs+ partly (local) $ref to simplify definition of recureing property types.

readonly does not work for checkboxes

nested object properties

support of recursive object-types in json-schema like

{
  "type":"object",
  "properties": {
    "lastname": {"type": "string"},
    "firstname": {"type: "string"},
    "address": {"type": "object",
                "properties": {
    .....
   }
  [
}

Support of textarea

Support a textarea for huge strings

Remove leading and trailing blanks

hardcoded itemname in html

the itemname of the jsonregion is hardcoded.
Substitute by configured name

use more apex.widget....

Check whether it is possible to use more of the javascript-widgets

• widget.yesNo
• widget.starRating
• widget.selectList
• ...

Support of dependentSchemas

default labels with 1st char upper

display lables with same default format as APEX-page-designer.
Seperate to single words, 1st char upper, rest lower.
"created_at" > "Created At"

Oracle 23c JSON-schema and date

Oracle uses in the JSON-schema for validating a JSON for validation date values an new type

...
{
   "extendedType"="date".
   ...
}

JSON-schema docu specifies here

...
{
  "type": "string", 
  "format="date",
  ...
}

This extendedType must be handled properly.

Support of theming

Theming of the UI does not always work.

APEX-22.1 has another date/time-picker

APEX.22.1 uses another date/timepicker than APEX >=22.2.
So date/date-time do not work with APEX <22.2

textarea with markdown- and/or richttext-editor

optionally use
markdown or richttext editor for textareas.

this seems to be tricky and APEX-release dependent.

Refresh JSON-region on demand

Plugin is only initiallized when page is displayed first.

It should be possible to change content of region with an event (click, changed data, ...) or on demand

config of dataitem in Source-attribute

Use the default Source-attribute for confioguration of the dataitem containing the JSON.

Caution: not compatible fir older versions.

Reduce logging to browser console

To much logging to Browser console.
Set more logs to trace

additional UI-items

Support of optional UI-item-types

• boolean attributes switch
• integer starrating
• long strings markdown-editor instead of textarea

support of conditional JSON-schema "IF", "THEN", "ELSE"

Support of conditions schema

Idea:
Depending on a type property parts of the UI are hidden.

Example:
Property
"differentBillingaddress": "true"
requires the input of a 2nd address.

 ...
"address": {"$ref": "#/$defs/address"},
"differentBillingaddress": {"type": "boolean"},
"if":{
   "properties": {
     "differentBillingaddress": { "const": true }
   }
}.
"then": {
  "properties": {
    "billingAddress": {"$ref": "#/$defs/address"}
  }
},
...

Automatic JSON-schema with Oracle 23c

Oracle 23c supports a validation constraint for JSON-columns to check the data with a JSON-schema.
This JSON-schema should be used for an "automatic mode* .
The definition of such a column looks like

IS JSON VALIDATE '{
  "type"       : "object",
  "required": {"c1", "c2"],
  "properties": {
    "c1": {...},
    "c2": {...},
    "c3": {...},
   ----
}'

array of "simple properties" with checkboxes

1st step for array support

{
  "type":"object",
  "properties": {
    "lastname": {"type": "string"},
    "firstname": {"type: "string"},
    "prop": {
      "type": "array",
      "items": { "type": "string", "enum": ["sel1", "sel2", ...]
   }
}

#2

wrong quoting of "

The character " is lost when saving a string fields

display of date/date-time and numbers in local format

Currently date/date-time are displays in ISO-format and number in plain format like it is stored in the JSON.