Skip to content

Update ChangeLog.md #2838

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
hlayisanimazuze wants to merge 1 commit into
base: releases/0.43
Choose a base branch
from
Open

Update ChangeLog.md #2838

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 9 additions & 4 deletions ChangeLog.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,8 +2,12 @@
# Release Notes
## 🚀 What's New in Shesha
- **Multi Entity Reference (Many-to-Many Reference)**
- Multi-Entity Reference allows an entity to maintain relationships with multiple related entities which can be applied to list properties.

- Multi-Entity Reference allows an entity to maintain relationships with multiple related entities which can be applied to list properties. For more details [see docs](https://docs.shesha.io/docs/back-end-basics/multi-entity-reference/)
- Support for multi-entity reference properties at the domain level. Developers can now define properties `(e.g., List<Persons> AssignedPeople)` with the `[MultiEntityReference]` attribute.
- GET, CREATE, and UPDATE operations now support multi-entity reference data. During updates, any references missing from the payload are automatically removed from the database.
- All multi-entity references are stored in a dedicated database table—no additional migrations required.
- The Entity Picker component now seamlessly bind to these properties, with the Autocomplete defaulting to multiple selections when applicable. The same binding mechanisim will be applied to Autocomplete component in the future release
- Changes to audited properties are now logged, and the entity configurator has been updated to reflect this new property type.
## 💪 Enhancements
- **Enhanced File List Display Options**
- The file list component now supports additional properties for improved customization. Users can choose between Thumbnail and File Name views.
Expand All @@ -12,9 +16,10 @@ Thumbnail view:
![Thumbnail_view](https://github.com/user-attachments/assets/7ab39a6e-9ab0-4a0b-a304-349fda212b52)

- **File Type Icons For Enhanced File List Component**
- We have improved the file list component by introducing file-specific icons for better clarity and user experience. Instead of the generic icon, the component now displays an appropriate icon based on the file type (e.g PDF, Word, Excel, Text files, and images). For unsupported file types, a default icon will be shown.
- We have improved the file list component by introducing file-specific icons for better clarity and user experience. Instead of the generic icon, the component now displays an appropriate icon based on the file type (e.g PDF, Word, Excel, Text files, and images). For unsupported file types, a default icon will be shown.
![image](https://github.com/user-attachments/assets/bbaa9f57-d8fd-4645-879c-4269d759606e)

- Added usage of `localStorage` and `sessionStorage` objects via `contexts.webStorage` from the Code Editor
- Limited script execution in components based on dependencies

## 🐞 Bug Fixes
- Fixed an issue where form arguments in custom buttons were not triggered when the DataTable changed in a modal dialog.
Expand Down