Support non-`id` primary keys

[jamesremuscat]

It looks like Admiral is hard-coded to expect an id attribute to be the primary key for data.

admiral/admiral/dataTable/DataTable.tsx

Line 281 in e58118b

rowKey="id"

admiral/admiral/crud/index.tsx

Line 55 in e58118b

pathname={`${config.path}/${record.id}`}

admiral/admiral/crud/index.tsx

Line 63 in e58118b

id={record.id}

This is an issue if using an API with a different name for the primary key! (For example, I'm trying to work with objects that have sessionID as their primary key.)

It would be useful to be able to specify this as part of a CRUD definition.

[mr-bantsevich]

Thanks for your interest and your question!

We have built the application architecture in such a way that circles and queries sent within them are built based on the passed ´path´ and ´id´.
Queries to retrieve table data must return a string ´id´ in the data structure. This ´id´ is used for further logic, e.g. for actions in the table.

At the moment we have this architecture and it will be quite expensive to change it. We have to make changes in a large part of the application.
But if there are desires to be a contributor, you are welcome!