A package that brings data-binding to your Unity project.
- About
- Folder Structure
- Installation
- Introduction
- Quick start
- How To Use
- External Assets
- Performance
- Contributing
- License
The UnityMvvmToolkit allows you to use data binding to establish a connection between the app UI and the data it displays. This is a simple and consistent way to achieve clean separation of business logic from UI. Use the samples as a starting point for understanding how to utilize the package.
Key features:
- Runtime data-binding
- UI Toolkit & uGUI integration
- Multiple-properties binding
- Custom UI Elements support
- Compatible with UniTask
- Mono & IL2CPP support*
The following example shows the UnityMvvmToolkit in action using the Counter app.
CounterView
<UXML>
<BindableContentPage binding-theme-mode-path="ThemeMode" class="counter-screen">
<VisualElement class="number-container">
<BindableCountLabel binding-text-path="Count" class="count-label count-label--animation" />
</VisualElement>
<BindableThemeSwitcher binding-value-path="ThemeMode, Converter={ThemeModeToBoolConverter}" />
<BindableCounterSlider increment-command="IncrementCommand" decrement-command="DecrementCommand" />
</BindableContentPage>
</UXML>
Note: The namespaces are omitted to make the example more readable.
CounterViewModel
public class CounterViewModel : IBindingContext
{
public CounterViewModel()
{
Count = new Property<int>();
ThemeMode = new Property<ThemeMode>();
IncrementCommand = new Command(IncrementCount);
DecrementCommand = new Command(DecrementCount);
}
public IProperty<int> Count { get; }
public IProperty<ThemeMode> ThemeMode { get; }
public ICommand IncrementCommand { get; }
public ICommand DecrementCommand { get; }
private void IncrementCount() => Count.Value++;
private void DecrementCount() => Count.Value--;
}
Counter | Calculator | ToDoList |
UnityMvvmCounter.mp4 |
UnityMvvmCalc.mp4 |
UnityMvvmToDoList.mp4 |
You will find all the samples in the
samples
folder.
.
├── samples
│ ├── Unity.Mvvm.Calc
│ ├── Unity.Mvvm.Counter
│ ├── Unity.Mvvm.ToDoList
│ └── Unity.Mvvm.CounterLegacy
│
├── src
│ ├── UnityMvvmToolkit.Core
│ └── UnityMvvmToolkit.UnityPackage
│ ...
│ ├── Core # Auto-generated
│ ├── Common
│ ├── External
│ ├── UGUI
│ └── UITK
│
├── UnityMvvmToolkit.sln
You can install UnityMvvmToolkit in one of the following ways:
1. Install via Package Manager
The package is available on the OpenUPM.
-
Open
Edit/Project Settings/Package Manager
-
Add a new
Scoped Registry
(or edit the existing OpenUPM entry)Name package.openupm.com URL https://package.openupm.com Scope(s) com.cysharp.unitask com.chebanovdd.unitymvvmtoolkit
-
Open
Window/Package Manager
-
Select
My Registries
-
Install
UniTask
andUnityMvvmToolkit
packages
2. Install via Git URL
You can add https://github.com/ChebanovDD/UnityMvvmToolkit.git?path=src/UnityMvvmToolkit.UnityPackage/Assets/Plugins/UnityMvvmToolkit
to the Package Manager.
If you want to set a target version, UnityMvvmToolkit uses the v*.*.*
release tag, so you can specify a version like #v1.0.0
. For example https://github.com/ChebanovDD/UnityMvvmToolkit.git?path=src/UnityMvvmToolkit.UnityPackage/Assets/Plugins/UnityMvvmToolkit#v1.0.0
.
The UnityMvvmToolkit uses generic virtual methods under the hood to create bindable properties, but IL2CPP
in Unity 2021
does not support Full Generic Sharing this restriction will be removed in Unity 2022
.
To work around this issue in Unity 2021
you need to change the IL2CPP Code Generation
setting in the Build Settings
window to Faster (smaller) builds
.
The package contains a collection of standard, self-contained, lightweight types that provide a starting implementation for building apps using the MVVM pattern.
The included types are:
- IBindingContext
- CanvasView<TBindingContext>
- DocumentView<TBindingContext>
- Property<T> & ReadOnlyProperty<T>
- Command & Command<T>
- AsyncCommand & AsyncCommand<T>
- AsyncLazyCommand & AsyncLazyCommand<T>
- PropertyValueConverter<TSourceType, TTargetType>
- ParameterValueConverter<TTargetType>
- IProperty<T> & IReadOnlyProperty<T>
- ICommand & ICommand<T>
- IAsyncCommand & IAsyncCommand<T>
- IPropertyValueConverter<TSourceType, TTargetType>
- IParameterValueConverter<TTargetType>
The IBindingContext
is a base interface for ViewModels. It is a marker for Views that the class contains observable properties to bind to.
Note: In case your ViewModel doesn't have a parameterless constructor, you need to override the
GetBindingContext
method in the View.
Here's an example of how to implement notification support to a custom property.
public class CounterViewModel : IBindingContext
{
public CounterViewModel()
{
Count = new Property<int>();
}
public IProperty<int> Count { get; }
}
A common scenario, for instance, when working with collection items, is to create a wrapping "bindable" item model that relays properties of the collection item model, and raises the property value changed notifications when needed.
public class ItemViewModel : IBindingContext
{
[Observable(nameof(Name))]
private readonly IProperty<string> _name = new Property<string>();
public string Name
{
get => _name.Value;
set => _name.Value = value;
}
}
The ItemViewModel
can be serialized and deserialized without any issues.
The CanvasView<TBindingContext>
is a base class for uGUI
views.
Key functionality:
- Provides a base implementation for
Canvas
based view - Automatically searches for bindable UI elements on the
Canvas
- Allows to override the base viewmodel instance creation
- Allows to define property & parameter value converters
public class CounterView : CanvasView<CounterViewModel>
{
// Override the base viewmodel instance creation.
// Required in case the viewmodel doesn't have a parameterless constructor.
protected override CounterViewModel GetBindingContext()
{
return _appContext.Resolve<CounterViewModel>();
}
// Define 'property' & 'parameter' value converters.
protected override IValueConverter[] GetValueConverters()
{
return _appContext.Resolve<IValueConverter[]>();
}
}
The DocumentView<TBindingContext>
is a base class for UI Toolkit
views.
Key functionality:
- Provides a base implementation for
UI Document
based view - Automatically searches for bindable UI elements on the
UI Document
- Allows to override the base viewmodel instance creation
- Allows to define property & parameter value converters
public class CounterView : DocumentView<CounterViewModel>
{
// Override the base viewmodel instance creation.
// Required in case the viewmodel doesn't have a parameterless constructor.
protected override CounterViewModel GetBindingContext()
{
return _appContext.Resolve<CounterViewModel>();
}
// Define 'property' & 'parameter' value converters.
protected override IValueConverter[] GetValueConverters()
{
return _appContext.Resolve<IValueConverter[]>();
}
}
The Property<T>
and ReadOnlyProperty<T>
provide a way to bind properties between a ViewModel and UI elements.
Key functionality:
- Provide a base implementation of the
IBaseProperty
interface - Implement the
IProperty<T>
&IReadOnlyProperty<T>
interface, which exposes aValueChanged
event
The following shows how to set up a simple observable property:
The Command
and Command<T>
are ICommand
implementations that can expose a method or delegate to the view. These types act as a way to bind commands between the viewmodel and UI elements.
Key functionality:
- Provide a base implementation of the
ICommand
interface - Implement the
ICommand
&ICommand<T>
interface, which exposes aRaiseCanExecuteChanged
method to raise theCanExecuteChanged
event - Expose constructor taking delegates like
Action
andAction<T>
, which allow the wrapping of standard methods and lambda expressions
The following shows how to set up a simple command.
using UnityMvvmToolkit.Core;
using UnityMvvmToolkit.Core.Interfaces;
public class CounterViewModel : IBindingContext
{
public CounterViewModel()
{
Count = new Property<int>();
IncrementCommand = new Command(IncrementCount);
}
public IProperty<int> Count { get; }
public ICommand IncrementCommand { get; }
private void IncrementCount() => Count.Value++;
}
And the relative UI could then be.
<ui:UXML xmlns:uitk="UnityMvvmToolkit.UITK.BindableUIElements" ...>
<uitk:BindableLabel binding-text-path="Count" />
<uitk:BindableButton command="IncrementCommand" />
</ui:UXML>
The BindableButton
binds to the ICommand
in the viewmodel, which wraps the private IncrementCount
method. The BindableLabel
displays the value of the Count
property and is updated every time the property value changes.
Note: You need to define
IntToStrConverter
to convert int to string. See the PropertyValueConverter section for more information.
The AsyncCommand
and AsyncCommand<T>
are ICommand
implementations that extend the functionalities offered by Command
, with support for asynchronous operations.
Key functionality:
- Extend the functionalities of the synchronous commands included in the package, with support for UniTask-returning delegates
- Can wrap asynchronous functions with a
CancellationToken
parameter to support cancelation, and they expose aDisableOnExecution
property, as well as aCancel
method - Implement the
IAsyncCommand
&IAsyncCommand<T>
interfaces, which allows to replace a command with a custom implementation, if needed
Let's say we want to download an image from the web and display it as soon as it downloads.
public class ImageViewerViewModel : IBindingContext
{
[Observable(nameof(Image))]
private readonly IProperty<Texture2D> _image;
private readonly IImageDownloader _imageDownloader;
public ImageViewerViewModel(IImageDownloader imageDownloader)
{
_image = new Property<Texture2D>();
_imageDownloader = imageDownloader;
DownloadImageCommand = new AsyncCommand(DownloadImageAsync);
}
public Texture2D Image => _image.Value;
public IAsyncCommand DownloadImageCommand { get; }
private async UniTask DownloadImageAsync(CancellationToken cancellationToken)
{
_image.Value = await _imageDownloader.DownloadRandomImageAsync(cancellationToken);
}
}
With the related UI code.
<ui:UXML xmlns:uitk="UnityMvvmToolkit.UITK.BindableUIElements" ...>
<BindableImage binding-image-path="Image" />
<uitk:BindableButton command="DownloadImageCommand">
<ui:Label text="Download Image" />
</uitk:BindableButton>
</ui:UXML>
Note: The
BindableImage
is a custom control from the create custom control section.
To disable the BindableButton
while an async operation is running, simply set the DisableOnExecution
property of the AsyncCommand
to true
.
public class ImageViewerViewModel : IBindingContext
{
public ImageViewerViewModel(IImageDownloader imageDownloader)
{
...
DownloadImageCommand = new AsyncCommand(DownloadImageAsync) { DisableOnExecution = true };
}
}
If you want to create an async command that supports cancellation, use the WithCancellation
extension method.
public class MyViewModel : IBindingContext
{
public MyViewModel()
{
MyAsyncCommand = new AsyncCommand(DoSomethingAsync).WithCancellation();
CancelCommand = new Command(Cancel);
}
public IAsyncCommand MyAsyncCommand { get; }
public ICommand CancelCommand { get; }
private async UniTask DoSomethingAsync(CancellationToken cancellationToken)
{
...
}
private void Cancel()
{
// If the underlying command is not running, or
// if it does not support cancellation, this method will perform no action.
MyAsyncCommand.Cancel();
}
}
If the command supports cancellation, previous invocations will automatically be canceled if a new one is started.
Note: You need to import the UniTask package in order to use async commands.
The AsyncLazyCommand
and AsyncLazyCommand<T>
are have the same functionality as the AsyncCommand
's, except they prevent the same async command from being invoked concurrently multiple times.
Let's imagine a scenario similar to the one described in the AsyncCommand
sample, but a user clicks the Download Image
button several times while the async operation is running. In this case, AsyncLazyCommand
will ignore all clicks until previous async operation has completed.
Note: You need to import the UniTask package in order to use async commands.
Property value converter provides a way to apply custom logic to a property binding.
Built-in property value converters:
- IntToStrConverter
- FloatToStrConverter
If you want to create your own property value converter, create a class that inherits the PropertyValueConverter<TSourceType, TTargetType>
abstract class and then implement the Convert
and ConvertBack
methods.
public enum ThemeMode
{
Light = 0,
Dark = 1
}
public class ThemeModeToBoolConverter : PropertyValueConverter<ThemeMode, bool>
{
// From source to target.
public override bool Convert(ThemeMode value)
{
return (int) value == 1;
}
// From target to source.
public override ThemeMode ConvertBack(bool value)
{
return (ThemeMode) (value ? 1 : 0);
}
}
Don't forget to register the ThemeModeToBoolConverter
in the view.
public class MyView : DocumentView<MyViewModel>
{
protected override IValueConverter[] GetValueConverters()
{
return new IValueConverter[] { new ThemeModeToBoolConverter() };
}
}
Then you can use the ThemeModeToBoolConverter
as in the following example.
<UXML>
<!--Full expression-->
<MyBindableElement binding-value-path="ThemeMode, Converter={ThemeModeToBoolConverter}" />
<!--Short expression-->
<MyBindableElement binding-value-path="ThemeMode, ThemeModeToBoolConverter" />
<!--Minimal expression - the first appropriate converter will be used-->
<MyBindableElement binding-value-path="ThemeMode" />
</UXML>
Parameter value converter allows to convert a command parameter.
Built-in parameter value converters:
- ParameterToIntConverter
- ParameterToFloatConverter
By default, the converter is not needed if your command has a string
parameter type.
public class MyViewModel : IBindingContext
{
public MyViewModel()
{
PrintParameterCommand = new Command<string>(PrintParameter);
}
public ICommand<string> PrintParameterCommand { get; }
private void PrintParameter(string parameter)
{
Debug.Log(parameter);
}
}
<UXML>
<BindableButton command="PrintParameterCommand, Parameter={MyParameter}" />
<!--or-->
<BindableButton command="PrintParameterCommand, MyParameter" />
</UXML>
If you want to create your own parameter value converter, create a class that inherits the ParameterValueConverter<TTargetType>
abstract class and then implement the Convert
method.
public class ParameterToIntConverter : ParameterValueConverter<int>
{
public override int Convert(string parameter)
{
return int.Parse(parameter);
}
}
Don't forget to register the ParameterToIntConverter
in the view.
public class MyView : DocumentView<MyViewModel>
{
protected override IValueConverter[] GetValueConverters()
{
return new IValueConverter[] { new ParameterToIntConverter() };
}
}
Then you can use the ParameterToIntConverter
as in the following example.
public class MyViewModel : IBindingContext
{
public MyViewModel()
{
PrintParameterCommand = new Command<int>(PrintParameter);
}
public ICommand<int> PrintParameterCommand { get; }
private void PrintParameter(int parameter)
{
Debug.Log(parameter);
}
}
<UXML>
<!--Full expression-->
<BindableButton command="PrintIntParameterCommand, Parameter={5}, Converter={ParameterToIntConverter}" />
<!--Short expression-->
<BindableButton command="PrintIntParameterCommand, 5, ParameterToIntConverter" />
<!--Minimal expression - the first appropriate converter will be used-->
<BindableButton command="PrintIntParameterCommand, 5" />
</UXML>
Once the UnityMVVMToolkit
is installed, create a class MyFirstViewModel
that implements the IBindingContext
interface.
using UnityMvvmToolkit.Core;
public class MyFirstViewModel : IBindingContext
{
public MyFirstViewModel()
{
Text = new ReadOnlyProperty<string>("Hello World");
}
public IReadOnlyProperty<string> Text { get; }
}
The next step is to create a class MyFirstDocumentView
that inherits the DocumentView<TBindingContext>
class.
using UnityMvvmToolkit.UITK;
public class MyFirstDocumentView : DocumentView<MyFirstViewModel>
{
}
Then create a file MyFirstView.uxml
, add a BindableLabel
control and set the binding-text-path
to Text
.
<ui:UXML xmlns:uitk="UnityMvvmToolkit.UITK.BindableUIElements" ...>
<uitk:BindableLabel binding-text-path="Text" />
</ui:UXML>
Finally, add UI Document
to the scene, set the MyFirstView.uxml
as a Source Asset
and add the MyFirstDocumentView
component to it.
For the uGUI
do the following. Create a class MyFirstCanvasView
that inherits the CanvasView<TBindingContext>
class.
using UnityMvvmToolkit.UGUI;
public class MyFirstCanvasView : CanvasView<MyFirstViewModel>
{
}
Then add a Canvas
to the scene, and add the MyFirstCanvasView
component to it.
Finally, add a Text - TextMeshPro
UI element to the canvas, add the BindableLabel
component to it and set the BindingTextPath
to Text
.
The package contains a set of standard bindable UI elements out of the box.
The included UI elements are:
Note: The
BindableListView
&BindableScrollView
are provided forUI Toolkit
only.
The BindableLabel
element uses the OneWay
binding by default.
public class LabelViewModel : IBindingContext
{
public LabelViewModel()
{
IntValue = new Property<int>(55);
StrValue = new Property<string>("69");
}
public IReadOnlyProperty<int> IntValue { get; }
public IReadOnlyProperty<string> StrValue { get; }
}
public class LabelView : DocumentView<LabelViewModel>
{
protected override IValueConverter[] GetValueConverters()
{
return new IValueConverter[] { new IntToStrConverter() };
}
}
<ui:UXML xmlns:uitk="UnityMvvmToolkit.UITK.BindableUIElements" ...>
<uitk:BindableLabel binding-text-path="StrValue" />
<uitk:BindableLabel binding-text-path="IntValue" />
</ui:UXML>
The BindableTextField
element uses the TwoWay
binding by default.
public class TextFieldViewModel : IBindingContext
{
public TextFieldViewModel()
{
TextValue = new Property<string>();
}
public IProperty<string> TextValue { get; }
}
<ui:UXML xmlns:uitk="UnityMvvmToolkit.UITK.BindableUIElements" ...>
<uitk:BindableTextField binding-text-path="TextValue" />
</ui:UXML>
The BindableButton
can be bound to the following commands:
To pass a parameter to the viewmodel, see the ParameterValueConverter section.
The BindableListView
control is the most efficient way to create lists. It uses virtualization and creates VisualElements only for visible items. Use the binding-items-source-path
of the BindableListView
to bind to an ObservableCollection
.
The following example demonstrates how to bind to a collection of users with BindableListView
.
Create a main UI Document
named UsersView.uxml
with the following content.
<ui:UXML xmlns:uitk="UnityMvvmToolkit.UITK.BindableUIElements" ...>
<uitk:BindableListView binding-items-source-path="Users" />
</ui:UXML>
Create a UI Document
named UserItemView.uxml
for the individual items in the list.
<ui:UXML xmlns:uitk="UnityMvvmToolkit.UITK.BindableUIElements" ...>
<uitk:BindableLabel binding-text-path="Name" />
</ui:UXML>
Create a UserItemViewModel
class that implements ICollectionItem
to store user data.
public class UserItemViewModel : ICollectionItem
{
[Observable(nameof(Name))]
private readonly IProperty<string> _name = new Property<string>();
public UserItemViewModel()
{
Id = Guid.NewGuid().GetHashCode();
}
public int Id { get; }
public string Name
{
get => _name.Value;
set => _name.Value = value;
}
}
Create a UserListView
that inherits the BindableListViewWrapper<TItemBindingContext>
abstract class.
public class UserListView : BindableListView<UserItemViewModel>
{
public new class UxmlFactory : UxmlFactory<UserListView, UxmlTraits> {}
}
Create a UsersViewModel
.
public class UsersViewModel : IBindableContext
{
public UsersViewModel()
{
var users = new ObservableCollection<UserItemViewModel>
{
new() { Name = "User 1" },
new() { Name = "User 2" },
new() { Name = "User 3" },
};
Users = new ReadOnlyProperty<ObservableCollection<UserItemViewModel>>(users);
}
public IReadOnlyProperty<ObservableCollection<UserItemViewModel>> Users { get; }
}
Create a UsersView
with the following content.
public class UsersView : DocumentView<UsersViewModel>
{
[SerializeField] private VisualTreeAsset _userItemViewAsset;
protected override IReadOnlyDictionary<Type, object> GetCollectionItemTemplates()
{
return new Dictionary<Type, object>
{
{ typeof(UserItemViewModel), _userItemViewAsset }
};
}
}
The BindableScrollView
has the same binding logic as the BindableListView
. It does not use virtualization and creates VisualElements for all items regardless of visibility.
Let's create a BindableImage
UI element.
First of all, create a base Image
class.
public class Image : VisualElement
{
public void SetImage(Texture2D image)
{
style.backgroundImage = new StyleBackground(image);
}
public new class UxmlFactory : UxmlFactory<Image, UxmlTraits> {}
public new class UxmlTraits : VisualElement.UxmlTraits {}
}
Then create a BindableImage
class and implement the data binding logic.
public class BindableImage : Image, IBindableElement
{
private PropertyBindingData _imagePathBindingData;
private IReadOnlyProperty<Texture2D> _imageProperty;
public string BindingImagePath { get; private set; }
public void SetBindingContext(IBindingContext context, IObjectProvider objectProvider)
{
_imagePathBindingData ??= BindingImagePath.ToPropertyBindingData();
_imageProperty = objectProvider.RentReadOnlyProperty<Texture2D>(context, _imagePathBindingData);
_imageProperty.ValueChanged += OnImageValueChanged;
SetImage(_imageProperty.Value);
}
public void ResetBindingContext(IObjectProvider objectProvider)
{
if (_imageProperty == null)
{
return;
}
_imageProperty.ValueChanged -= OnImageValueChanged;
objectProvider.ReturnReadOnlyProperty(_imageProperty);
_imageProperty = null;
SetImage(null);
}
private void OnImageValueChanged(object sender, Texture2D newImage)
{
SetImage(newImage);
}
public new class UxmlFactory : UxmlFactory<BindableImage, UxmlTraits> { }
public new class UxmlTraits : Image.UxmlTraits
{
private readonly UxmlStringAttributeDescription _bindingImageAttribute = new()
{ name = "binding-image-path", defaultValue = "" };
public override void Init(VisualElement visualElement, IUxmlAttributes bag, CreationContext context)
{
base.Init(visualElement, bag, context);
((BindableImage) visualElement).BindingImagePath = _bindingImageAttribute.GetValueFromBag(bag, context);
}
}
}
Now you can use the new UI element as following.
public class ImageViewerViewModel : IBindingContext
{
public ImageItemViewModel(Texture2D image)
{
Image = new ReadOnlyProperty<Texture2D>(image);
}
public IReadOnlyProperty<Texture2D> Image { get; }
}
<UXML>
<BindableImage binding-image-path="Image" />
</UXML>
To enable async commands support, you need to add the UniTask package to your project.
In addition to async commands UnityMvvmToolkit provides extensions to make USS transition's awaitable.
For example, your VisualElement
has the following transitions.
.panel--animation {
transition-property: opacity, padding-bottom;
transition-duration: 65ms, 150ms;
}
You can await
these transitions using several methods.
public async UniTask DeactivatePanel()
{
try
{
panel.style.opacity = 0;
panel.style.paddingBottom = 0;
// Await for the 'opacity' || 'paddingBottom' to end or cancel.
await panel.WaitForAnyTransitionEnd();
// Await for the 'opacity' & 'paddingBottom' to end or cancel.
await panel.WaitForAllTransitionsEnd();
// Await 150ms.
await panel.WaitForLongestTransitionEnd();
// Await 65ms.
await panel.WaitForTransitionEnd(0);
// Await for the 'paddingBottom' to end or cancel.
await panel.WaitForTransitionEnd(new StylePropertyName("padding-bottom"));
// Await for the 'paddingBottom' to end or cancel.
// Uses ReadOnlySpan to match property names to avoid memory allocation.
await panel.WaitForTransitionEnd(nameof(panel.style.paddingBottom));
// Await for the 'opacity' || 'paddingBottom' to end or cancel.
// You can write your own transition predicates, just implement a 'ITransitionPredicate' interface.
await panel.WaitForTransitionEnd(new TransitionAnyPredicate());
}
finally
{
panel.visible = false;
}
}
Note: All transition extensions have a
timeoutMs
parameter (default value is2500ms
).
The UnityMvvmToolkit uses object pools under the hood and reuses created objects. You can warm up certain objects in advance to avoid allocations during execution time.
public abstract class BaseView<TBindingContext> : DocumentView<TBindingContext>
where TBindingContext : class, IBindingContext
{
protected override IObjectProvider GetObjectProvider()
{
return new BindingContextObjectProvider(new IValueConverter[] { new IntToStrConverter() })
// Finds and warmups all classes from calling assembly that implement IBindingContext.
.WarmupAssemblyViewModels()
// Finds and warmups all classes from certain assembly that implement IBindingContext.
.WarmupAssemblyViewModels(Assembly.GetExecutingAssembly())
// Warmups a certain class.
.WarmupViewModel<CounterViewModel>()
// Warmups a certain class.
.WarmupViewModel(typeof(CounterViewModel))
// Creates 5 instances to rent 'IProperty<string>' without any allocations.
.WarmupValueConverter<IntToStrConverter>(5);
}
}
You may contribute in several ways like creating new features, fixing bugs or improving documentation and examples.
Use discussions to have conversations and post answers without opening issues.
Discussions is a place to:
- Share ideas
- Ask questions
- Engage with other community members
If you find a bug in the source code, please create bug report.
Please browse existing issues to see whether a bug has previously been reported.
If you have an idea, or you're missing a capability that would make development easier, please submit feature request.
If a similar feature request already exists, don't forget to leave a "+1" or add additional information, such as your thoughts and vision about the feature.
Give a ⭐ if this project helped you!
Usage is provided under the MIT License.