[CLOSED] [#233] Cannot bind DataIndex starting with case letter in TreePanel

[millenovanta]

I've a TreePanel (a GridPanel), where i pass data as a NodeCollection, via proxy, where fields data are declared in attributeObject (is it ocrrect?).

Main.Models.LegDTO a = new LegDTO();
                    a.legID = 2;
                    a.LegCodice = "aaaaaa";

                    asyncNode.AttributesObject = a;

Binding:

Html.X().Column()
                                        .Text("LegCodice")
                                        .DataIndex("LegCodice")

If the attribute starts with case letter, binding doesn't work, if it doesn't start with case letter, it does work.

If I write 'legCodice' everywhere (in the DTO Entity, in the dataIndex, and in the AttributeObject), it works. If I use LegCodice, it does not work.
Is this a bug or I'm losing something?

[Baidaly]

Hello!

Try to use CustomAttributes instead of AttributesObject

[millenovanta]

Thank you.

How can I convert a generic T Entity in a a ConfigItemCollection?

Now I'm using

node.AttributesObject = record

where record is of type T.

It compiles because AttributesObject expects an object.

But CustomAttributes requires a ConfigItemCollection.
How can i So convert T in a ConfigItemCollection?

TY

[Daniil]

Please try:

Main.Models.LegDTO a = new LegDTO();
a.legID = 2;
a.LegCodice = "aaaaaa";

asyncNode.CustomAttributes.Add(a);

[Daniil]

Generally, converting the first letter to be lowercase is a common thing across the library. It is because of JavaScript convention to start property names from a lowercase letter.

But it should be configurable. I created an Issue.
https://github.com/extnet/Ext.NET/issues/233

[millenovanta]

Using custom attributes, it works quite well. Anyway, I'm watching for a good architecture, so I would like to understand if using customAttributes is a good way or just a workaround.
Should it be better to use attributesObejct?
I'm using codefirst to define entities and to map fields on db. Which convention should be used to define Entitie's properties names?
Should they be lower case?

Thank you again!

[Daniil]

Using CustomAttributes is not a workaround, it can be a permanent solution.

Should it be better to use attributesObejct?

Well, no. They actually do the same. Just an AttributesObject is serialized with lowercase first letters.

Which convention should be used to define Entitie's properties names?
Should they be lower case?

Personally, I would follow .NET property naming convention, i.e. uppercase first letters. Well, as you already did.

[millenovanta]

I will do so. Thank you!

[Baidaly]

Hello!

We added new property AttributesCamelCase to Node class which you can use to solve your issue.

Please, update from SVN and retest.

[millenovanta]

Thank you.
I have no access to svn repo. There is a way to test it?

M