-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support non-id
primary keys
#116
Comments
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´. 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. |
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
admiral/admiral/crud/index.tsx
Line 55 in e58118b
admiral/admiral/crud/index.tsx
Line 63 in e58118b
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.
The text was updated successfully, but these errors were encountered: