dmx-platform issueshttps://git.dmx.systems/dmx-platform/dmx-platform/-/issues2024-03-02T21:44:34+01:00https://git.dmx.systems/dmx-platform/dmx-platform/-/issues/537Revise Files API2024-03-02T21:44:34+01:00Jörg RichterRevise Files APIThe current Files API (DMX 5.3.4) does not support the use case described in dmx-plugins/dmx-linqa#38 very well, that is **transforming an uploaded file before storing** it in DMX file repo. The Files API should be revised.
@jpn FYIThe current Files API (DMX 5.3.4) does not support the use case described in dmx-plugins/dmx-linqa#38 very well, that is **transforming an uploaded file before storing** it in DMX file repo. The Files API should be revised.
@jpn FYIDMX 5.3.5Jörg RichterJörg Richterhttps://git.dmx.systems/dmx-platform/dmx-platform/-/issues/535Revise resource handling2024-02-22T23:33:14+01:00Jörg RichterRevise resource handlingCurrent resource handling (#504) is still not optimal.
The current approach causes confusion about
a) how webpack output coexists with static web resources, and
b) how to control what to include in git repo.
Webpack output should ...Current resource handling (#504) is still not optimal.
The current approach causes confusion about
a) how webpack output coexists with static web resources, and
b) how to control what to include in git repo.
Webpack output should go to `target/`, not `src/`.
`src/main/resources/web/` should not be .gitignored.
The `resources-static/` directory is possibly not needed then.
See https://git.dmx.systems/dmx-plugins/dmx-sign-up-ui/-/issues/15#note_26032
@rsc FYIDMX 5.3.4Jörg RichterJörg Richterhttps://git.dmx.systems/dmx-platform/dmx-platform/-/issues/452Core API: improve getChildTopics() experience2021-06-23T16:20:13+02:00Jörg RichterCore API: improve getChildTopics() experienceIn particular the error messages should better differentiate between "type Y has no comp def X" and "missing value for comp def X".
This is a follow-up of a [forum posting](https://forum.dmx.systems/t/optionally-getting-a-string-from-a-...In particular the error messages should better differentiate between "type Y has no comp def X" and "missing value for comp def X".
This is a follow-up of a [forum posting](https://forum.dmx.systems/t/optionally-getting-a-string-from-a-topic/112).
@rsc @mukil FYIJörg RichterJörg Richterhttps://git.dmx.systems/dmx-platform/dmx-platform/-/issues/341API Consolidation2023-11-18T00:02:26+01:00Jörg RichterAPI ConsolidationMain focus for DMX 5.0 final is API Consolidation.
Affected:
- Java API
- REST API
- Client-side APIs (Webclient, general purpose libraries and GUI components)
This ticket documents the API changes introduced since 5.0-beta-7.
@mukil FYIMain focus for DMX 5.0 final is API Consolidation.
Affected:
- Java API
- REST API
- Client-side APIs (Webclient, general purpose libraries and GUI components)
This ticket documents the API changes introduced since 5.0-beta-7.
@mukil FYIDMX 5.0Jörg RichterJörg Richterhttps://git.dmx.systems/dmx-platform/dmx-platform/-/issues/292Let plugins configure a server-side update logic on a per-type basis2019-10-07T16:28:39+02:00Jörg RichterLet plugins configure a server-side update logic on a per-type basisAs an example consider an update-user-account request (#97): clients would still send it to the generic update endpoint, and the Access Control plugin interferes the request at server-side (in order to do password's SHA256 encoding and p...As an example consider an update-user-account request (#97): clients would still send it to the generic update endpoint, and the Access Control plugin interferes the request at server-side (in order to do password's SHA256 encoding and proprietary workspace assignment).
An alternative approach would be to let the client send the update-user-account request to a *proprietary endpoint* (#98), provided by Access Control plugin. But then a chance for misuse remains: an application could still send an update-user-account request to the *generic update endpoint* by mistake. This would corrupt the user account. Server-side interference eliminates that error source.
So #98 will be postponed in favor for a server-side approach.
@mukil FYIJörg RichterJörg Richterhttps://git.dmx.systems/dmx-platform/dmx-platform/-/issues/269Plugin config mechanism2019-08-07T16:38:55+02:00Jörg RichterPlugin config mechanismAt the moment DMX has a global config file (`config.properties`). We need a per-plugin config mechanism.
It might be realized like this:
- The config files are named like the respective plugin, but without version number, e.g. `dmx-ldap...At the moment DMX has a global config file (`config.properties`). We need a per-plugin config mechanism.
It might be realized like this:
- The config files are named like the respective plugin, but without version number, e.g. `dmx-ldap.properties`.
- The config files are stored in the same directory as the global config file (as configured by `java.util.logging.config.file`). An alternative approach is storing them together with the respective plugin file (in `bundle-deploy`).
- When starting a plugin the Core reads its config file (if exists) and makes the therein defined properties available as Java system properties.
- Hot-Config: plugin config changes are active without restarting the platform (as it is required now). The Core re-reads the config when the plugin is restarted, e.g. by `refresh` gogo shell command. Alternatively the platform could scan the config directory periodically and propagate changes automatically (without manual refresh).
@jpn @mukil FYIJörg RichterJörg Richterhttps://git.dmx.systems/dmx-platform/dmx-platform/-/issues/98Let plugins provide custom form submit logic on a per-type basis2019-10-07T16:28:51+02:00Jörg RichterLet plugins provide custom form submit logic on a per-type basisA (client-side) plugin can provide a custom "form submitter" to take complete control about both, what data is sent on submit, and to what URL it is sent. A plugin does so by registering one or more form submitter(s) for certain topic/as...A (client-side) plugin can provide a custom "form submitter" to take complete control about both, what data is sent on submit, and to what URL it is sent. A plugin does so by registering one or more form submitter(s) for certain topic/assoc types.
@mukil FYIJörg RichterJörg Richter