Created collapsible record and collapsible record list#2309
Open
Toocky wants to merge 16 commits into
Open
Conversation
…ttps://github.com/Toocky/corteza into 2024.9.x-feature-collapsable-record-history-blocks
️✅ There are no secrets present in this pull request anymore.If these secrets were true positive and are still valid, we highly recommend you to revoke them. 🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request. |
Author
|
Rebased to 2024.9.8 |
…ttps://github.com/Toocky/corteza into 2024.9.x-feature-collapsable-record-history-blocks
…ttps://github.com/Toocky/corteza into 2024.9.x-feature-collapsable-record-history-blocks
…rd fields preferred names, fixed other fields defaulting to all and not none
parent reference field filter fixed
4eda56b to
f775bb1
Compare
b8536d1 to
b7d6d27
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.
The following changes are implemented
New block types
Collapsible Record:
configurable header with title and subtitle ( subtitle is selectable to include when minimised)
able to specify title alignment left centre right
3 choices for the main part of the record,
Single body of rich text the full width of the block
A collection of record fields ie current record
both body of text and selection of fields, with configurable position above below
can default collapsed
Collapsible Record List:
As the above collapses into a single header its possible to create a list of collapsed items
all the other features of a record list, sorting paging etc
This could allow for the creation of effective history record lists, ie a case history with the records sorted by date
#2308
https://forum.cortezaproject.org/t/collapsible-record-collapsible-record-list-blocks/3080
Changes in the user interface:
to allow manipulating the alignment in the title and subtitle i have modified the expressions to handle L[], C[], R[] to adjust alignment.
i.e.
L[${record.values.title}] to align left
C[example text] to align centre
R[${record.values.status} ${record.values.date}] to align right
all of these can be used in a single title, but they must be used once each and in the correct order, you can not use C[], R[], L[], it will ignore them and default to all left alignment
The single record block when collapsed will also redraw the page and draw up blocks below it assuming there is nothing else blocking the blocks below it
the list block is intended to be identical to the above just a list of the records collapsed to be expanded as the user wishes

There is room for improvement theres currently no editing options but for now i'm putting the PR in for any comments / suggestions as i want to get this pushed for my own use to see how it works in production also i need to rebase now there's been a new release
Checklist when submitting a final (!draft) PR