Eike Thies
Eike Thies
Wow what a quick response, respect :) I thought about implementing it myself, but wanted to first create a ticket. Anyway, thx and yes {{index}} is just the iterator number...
Interestingly it works in this case. ``` path: 'users', delete: false, randomize: false, templates: [{ id: counter(), group: 'user', email: '[email protected]', birthday: 1990, password: 'test123' }, { id: counter(), group:...
i'm silly, sry you're right. Just strange that it worked in the above example.
Well to be honest it can still be improved, just using {{index}} would be really great, but as a workaround this is legitimate. Maybe referecing this in the documentation at...
One remark: For now i'm just setting the id field manually myself to make sure it has a certain id. So this issue is not on high priority.
Sure feathers shouldn't be aware of any implementation details of the service adapters. But the hook would be great!
Sure i know, but the callbacks can get quite ugly, as in a relational database it might be that everything is kind of tangled with each other. Back to the...
that is exactly what i thought. i really think forcing some kind of order would be good for real-world use cases. sure with a relational db you will always run...
i am currently facing the same problem i think. i have a m2m relation and trying to clean up ghost entries which happen unfortunately when updating the relations. you can...
FYI: I had the same problem on FF, used chromium and it works _Environemnt: ubuntu 22.04 on hyper-v VM on windows 10 (good for testing caprover out)_