[FEATURE] UI: add Listing\Inline and Listing\Entity\Grid component.#11444
Open
thibsy wants to merge 1 commit intoILIAS-eLearning:release_10from
Open
[FEATURE] UI: add Listing\Inline and Listing\Entity\Grid component.#11444thibsy wants to merge 1 commit intoILIAS-eLearning:release_10from
Listing\Inline and Listing\Entity\Grid component.#11444thibsy wants to merge 1 commit intoILIAS-eLearning:release_10from
Conversation
6897338 to
e816414
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi all,
This PR introduces some new features to the UI framework. At its essence, the PR
Listing\InlinecomponentListing\Entity\GridcomponentEntity\Entity::withWorkflow()functionalityThis was spawned by the following background / motivation:
Entity\Entity::withWorkflow()functionality was our solution for the problem we see during object (or entity) creation, where an entity is created kind of as a skeleton, which is filled with content, configured, published, etc. only at a later point – maybe even stretched across several days. What becomes clear is that the object/entity-creation is actually a workflow most of the time. This is why the new functionality now combines these components to speak about this process semantically. The entity will derive "unfinished" steps from this workflow and present them to authors in a structured way. To implement this a newListing\Inlinecomponent was spawned as a byproduct (for horizontal display of properties).Listing\Entity\Gridcomponent was our solution for the realisation that user expectations for entity listings are different depending on their use-case. "Consumers" of an entity need a lighter, less detailed view than authors, who may need to see what steps of the entity creation workflow are still unfinished.Why we propose to integrate this for ILIAS 10:
We do not have everything in place to fully migrate the repository yet. Making these solutions available for plugins from ILIAS 10 will allow us to gather information for this migration beforehand. Namely this will be the OpenCast plugin, which provides its own sophisticated view inside the repository – making it the perfect candidate to test this before moving forward in ILIAS. There are no breaking changes for any usage of the components affected by the changes of this PR. However, there would be breaking changes for custom version of affected components, implemented by the plugin.
Kind regards,
@thibsy