Releases: LazZiya/TagHelpers
Releases · LazZiya/TagHelpers
4.0-preview1
This release contains many new features and breaking changes, read below instructions for all changes, or visit LazZiya.TagHelpers wiki for all documentations.
Improvements
PagingTagHelper
- Precise max-displayed-pages values (can set to 0, 1, 3 ...)
LanguageTagHelper
- Performance imrovements and bug fix for classic dropdown redirecting.
New
PagingTagHelper
- Ajax: PagingTagHelper now supports ajax
- number-format: Display numbers in different formats (decimal, hex, roman, arabic, hindi, ..etc)
- page-size-dropdown-items: Specify items for page size dropdown as a dash delimitted array "10-25-50"
LanguageNavTagHelper
- cookie-handler-url: Specify handler url to save current culture value in a cookie
- redirect-to-url: Use any url to redirect to on language change
- flags: Show country flags
Changes
Localization-Validation-Scripts:
- Manual registration: TagHelper component requires manually registration in startup.
Deprected
PagingTagHelper
- page-size-nav-block-size : use page-size-dropdown-items instead
- page-size-nav-max-items : use page-size-dropdown-items instead
- show-first-numbered-page : use show-gap instead
- show-last-numbered-page : use show-gap instead
- gap-size : use show-gap instead
- query-string-value : -
- page-size-nav-on-change : -
LanguageTagHelper
- culture-key-name : not required any more.
- redirect-to : use redirect-to-url instead.
- home-page-name : use redirect-to-url instead
3.1.2
3.1.1
3.1.0
3.1.0-preview2
New defaults for PagingTagHelper, all options are turned on, can be turned off manually if not needed. see the demo page for more details about PagingTagHelper options.
3.1.0-preview1
- Added support for DotNetCore 3.1
- Paging TagHelper :
query-string-value
is not required to be passed as parameter, the query string value will be automatically assigned by ViewContext in the TagHelper
3.0.2
3.0.1
3.0.0-preview1
- Added support for DotNetCore 3.0
- Auto RTL direction for LanguageTagHelper