Releases: TasoOneAsia/t-notify
v1.5.1
Bug Fixes
- add missing file (#19) #19 (RockySouthpaw)
Chores
- bump: Bump stable version to v1.5.1 (RockySouthpaw)
T-Notify v1.5.0
Features
- cd: GitHub action for automatic releases (Taso)
- docs: Change lightmode to simple dark (XiosBombay)
Continuous Integration
- releases: Automatically generate release on tag push (Taso)
Chores
Commits
T-Notify v1.4.2 - Hotfix Update Script
Changelog
- Fix error message being shown in update script at startup, even when we receive a 200 status code
T-Notify v1.4.1 - Update Persistent Notifications
Features
- Update an existing persistent notification using the step
update(Courtesy of @emileet). Here is an example:
exports['t-notify']:Persist({
id = 'uniquePersistId',
step = 'update',
options = {
style = 'info',
title = 'Notification with an Image',
message = 'Updated item',
sound = true,
position = 'top-left'
}
})Tweaks
- Slight tweaked the update script visuals
T-Notify v1.4.0 - Type Validation & Color Codes
New Features
Color Codes
Color codes have now been added as an additional markdown-like tag. Here is an example of how they are used.
exports['t-notify']:Custom({
style = 'message',
duration = 11000,
title = 'Colors Example',
message = '~r~Red~r~ \n ~g~Green~g~ \n ~y~Yellow~y~ \n ~b~Blue~b~ \n ~c~Cyan~c~ \n ~p~Purple~p~ \n ~w~White~w~ \n ~o~Orange~o~ \n ~gy~Grey~gy~ \n',
sound = true
})This produces the following notification:
Type Validation for Notification Properties
Type validation has also been added this release, which will inform you if the notification object has a property of the wrong type, before this was unhandled. Now there are verbose error messages.
Minor Tweaks/Fixes
- Fix an edge case when notifications would not properly show a title/message if that title or message was passed as a non-number.
- Error prints are now red
- Utilized FiveM color codes for the update script rather than ANSI Escape Codes so these format properly in svgui.
- General code cleanup for NUI
- General code cleanup for Lua
- Update docs with new color feature
Note
As always this update should be 100% backward compatible with past versions of T-Notify.
T-Notify v1.4.0-rc4 - Type Validation & Color Codes
The last major feature changes before v1.4.0, anything else will be bug fixes/minor tweaks.
This RC changes to a letter based color code system, see the example for more details.
New Features
Color Codes
Color codes have now been added as an additional markdown-like tag. Here is an example of how they are used.
exports['t-notify']:Custom({
style = 'message',
duration = 11000,
title = 'Colors Example',
message = '~r~Red~r~ \n ~g~Green~g~ \n ~y~Yellow~y~ \n ~b~Blue~b~ \n ~c~Cyan~c~ \n ~p~Purple~p~ \n ~w~White~w~ \n ~o~Orange~o~ \n ~gy~Grey~gy~ \n',
sound = true
})This produces the following notification:
Type Validation for Notification Properties
Type validation has also been added this release, which will inform you if the notification object has a property of the wrong type, before this was unhandled. Now there are verbose error messages.
Minor Tweaks/Fixes
- Fix an edge case when notifications would not properly show a title/message if that title or message was passed as a non-number.
- Error prints are now red
- Utilized FiveM color codes for the update script rather than ANSI Escape Codes so these format properly in svgui.
- General code cleanup for NUI
- General code cleanup for Lua
Note
As always this update should be 100% backward compatible with past versions of T-Notify. Documentation will be added before graduation to release.
This is a release candidate for testing purposes only, certain things may change before it is graduated to release. Do not use this in production
T-Notify v1.4.0-rc3 - Type Validation & Color Codes
This is probably the final release candidate for T-Notify v1.4.0, it includes several features and enhancements retaining standard semver backward compatibility.
New Features
Color Codes
Color codes have now been added as an additional markdown-like tag. Here is an example of how they are used.
exports['t-notify']:Custom({
style = 'message',
duration = 11000,
title = 'Colors Example',
message = '^1Red^1 \n^2Green^2 \n^3Yellow^3 \n^4Blue^4\n^5Cyan^5\n^6Purple^6 \n^7White^7 \n^8Orange^8 \n^9Grey^9\n',
sound = true
})This produces the following notification:
Type Validation for Notification Properties
Type validation has also been added this release, which will inform you if the notification object has a property of the wrong type, before this was unhandled. Now there are verbose error messages.
Minor Tweaks/Fixes
- Fix an edge case when notifications would not properly show a title/message if that title or message was passed as a non-number.
- Error prints are now red
- Utilized FiveM color codes for the update script rather than ANSI Escape Codes so these format properly in svgui.
- General code cleanup for NUI
- General code cleanup for Lua
Note
As always this update should be 100% backward compatible with past versions of T-Notify. Documentation will be added before graduation to release.
This is a release candidate for testing purposes only, certain things may change before it is graduated to release. Do not use this in production
T-Notify v1.4.0-rc2 - Minor
This changes a couple things from the last RC. Color codes remain the same but you must start and end color coded text with the color code.
For example ^1This text will all be red^1.
Misc
- Fix license shenanignas
- Tweak update script slightly to adhere to FiveM svgui color codes
T-Notify v1.4.0-rc1 - Minor
Features
- Added color codes that can be used as a markdown tag, these codes follow the FiveM specification as follows:
^1 is Red
^2 is Green
^3 is Yellow
^4 is Blue
^5 is Cyan
^6 is Purple
^7 is White
^8 is Orange
^9 is Grey
Note: This is a release candidate and is not meant for production application
T-Notify v1.3.2 (MINOR) - Minor fix
Fixes
- Fixed incorrect native casing that would cause an error, if passing the sound property as a table rather than a boolean.
As always, unlike almost everyone else in the FiveM community, T-Notify abides by Semantic Versioning, meaning this release is backwards compatible