Skip to content

Conversation

szabozoltan69
Copy link
Contributor

Addresses #2533

@szabozoltan69 szabozoltan69 force-pushed the feature/dref-less-data branch 4 times, most recently from 22b7ae6 to fe4aeb5 Compare August 19, 2025 12:06
@szabozoltan69 szabozoltan69 marked this pull request as ready for review August 19, 2025 12:08
@szabozoltan69 szabozoltan69 requested a review from susilnem August 19, 2025 12:08
@szabozoltan69 szabozoltan69 force-pushed the feature/dref-less-data branch from fe4aeb5 to 1481899 Compare August 19, 2025 13:41
@szabozoltan69
Copy link
Contributor Author

@susilnem @thenav56 – if you have better idea to fix the DREF m2m issue, I am open to it. Some urgency has this topic.

@szabozoltan69
Copy link
Contributor Author

@susilnem – do you have any comments for this one?

@susilnem
Copy link
Member

Hey @szabozoltan69 ,

I just looked into this and noticed that there’s still no schema generated for the id field of M2M relationships. Ideally, this should have been handled automatically by the serializer when passing the id for M2M fields.

image

As, previously it was done for the proposed actions.

image

Note

We might need to add some changes for these fields on the go-web-app.
Need to check this behavior for FK fields if this exists.

@szabozoltan69 szabozoltan69 force-pushed the develop branch 2 times, most recently from a6244e2 to 1c75b84 Compare October 3, 2025 14:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants