Change request: Change key value internal id
See original GitHub issuePerhaps this is already possible, but mirageJs adds an id to each entity.
For example : [{id: 1, name: 'test'}, {id: 2, name: 'test2'}]
In our setup we don’t use the id
as key, but changed this to uuid
and in some cases xid
.
Is it possible to change the name of the key mirageJS uses for the id value ? Per model / Entity?
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
change-request-id - Oxygen XML Editor
Use the change-request-id element to specify an identifier associated with the change request, such as an issue ID or ticket number.
Read more >Solved: How to get the Change Request's sys_id inside a Bu...
I have a Business Rule with a custom script. The task of this script is to get the JSON of a Change Request...
Read more >MDG: Object Ids in Change Request - SAP Blogs
Create dynamic internal tables. Fetch Key Value from table PHYSICAL_NAME. Kindly take a note of below points before considering above logic:.
Read more >Change Requests | Sage Intacct Developer
List information for change requests linked to the project change order with the ID PCO-66. Includes the sum of the change request prices, ......
Read more >How to change value of a request parameter in laravel
$request->name = "My Value!";. I use this code but does not work: $request->offsetSet('img', ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It’s not configurable at the moment. The relationships use it as foreign keys, so there’d need to be some work done to PR an option to configure the primary key.
@samselikoff ok thank you, I got it working extending the RestSerializer.
What I can’t seem to get working is dat the serializer works for all traffic.
The ‘application’ key should take care of that, but no luck there. So I’m stuck with calling serialize in each route request, what can be going wrong here?