iluvadev / pocketbaseclient Goto Github PK

The Number type in PocketBase maps to c# int type.
But:

• Number accepts any real and natural value; values with or without decimals
• int only accepts natural values in the range -2147483648 to 2147483647

With this mapping, there are no options to work with decimal values

Extend filters to support new PocketBase filters:

• ?= Any/At least one of Equal
• ?!= Any/At least one of NOT equal
• ?> Any/At least one of Greater than
• ?>= Any/At least one of Greater than or equal
• ?< Any/At least one of Less than or equal
• ?<= Any/At least one of Less than or equal
• ?~ Any/At least one of Like/Contains (if not specified auto wraps the right string OPERAND in a "%" for wildcard match)
• ?!~ Any/At least one of NOT Like/Contains (if not specified auto wraps the right string OPERAND in a "%" for wildcard match)

Make the generated code compatible with Unity
See: https://docs.unity3d.com/2019.1/Documentation/Manual/dotnetProfileSupport.html

Support expand records when gets from PocketBase.

Something like:

filteredPosts.Expand(p => p.Author)

At now, when a property value is modified, the object is marked as modified with local changes.
The save operation updates all object.

Actually:

• The entire object is saved
• There is no track about changes, and do not know if really the object is changed: A property can be changed again to its initial value

PocketBase allows field names that can not be translated correctly to Properties in C#:

• _ -> Is translated to Empty string
• __ -> Is translated to Empty string. Same PropertyName as _
• 1 -> Is translated to "1", forbidden name for a Property
• _1, 1_, _1_ -> All translated to "1", forbidden name for a Property. Same PropertyName as 1

And allows multiple fields that will be translated to the same Property name in C#:

• field, _field, __field, _field_ -> All translated to same PropertyName: Field
• my_field, my__field, _myField_, MyField -> All translated to same PropertyName: MyField