-
Notifications
You must be signed in to change notification settings - Fork 724
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
Pre-populate fields (for referenced_list) #627
Comments
Nope, note at the time, but that's a good idea for a PR ;) |
might have to dig in the code and add it then ;) What do you suggest for the process? I was thinking it would be cool to specify a listView object for a referenced_list, then you could specify the list actions, and any filters eg the targetReferenceField would be passed to the creation view of the list table. What do you think? maybe too ambitious in scope.. |
The listView idea would also help with another problem i have where I need to specify a url for a referenced_list. For example the api has a user: /users/123 and a list of friends at /users/123/friends/ I got it to work with an ugly hack:
but would prefer a more elegant solution |
Use another entity object for your referenced_list? |
thats what im doing above ("friends" are also "user" objects), but the url to access them is different, so I had to create a new entity. |
Maybe these issues should go to StackOverflow? François? (inc. #636) |
I have asked on SO - no answers yet :( |
That's a perfectly valid solution, not a hack ;) |
Is there a way to create an "add" button on a referenced_list that links to the creation page with the targetReferenceField prepopulated with the current id?
The text was updated successfully, but these errors were encountered: