Skip to content

feature: Update WithIncludeOperations to not disable edges #106

@HaackTheSystem

Description

@HaackTheSystem

✨ Describe the feature you'd like

It would be useful to either have WithIncludeOperations not disable endpoints on edges, or have some sort of way to toggle the edges to still generate endpoints. Bonus points if there's a way to only do this for some edges but not all of them.

🌧 Is your feature request related to a problem?

Right now, I have an object where I am pulling data from another system and I would like that to remain the source of truth. However, I would like the ability to easily allow updating of SOME edges while disallowing edits to fields.

🔎 Describe alternatives you've considered

Option A: don't disable any endpoints using WithIncludeOperations, and just manually write hooks to check for updates to anything but specific edges, and disallow anything I don't want
Option B: Have my front end handle all edges on the side that doesn't have anything disabled, but it would be a bit more cumbersome to manage adds and deletes across multiple objects as it becomes an N:1 edge

⚠ If implemented, do you think this feature will be a breaking change to users?

Not sure

⚙ Additional context

No response

🤝 Requirements

  • I have confirmed that someone else has not submitted a similar feature request.
  • If implemented, I believe this feature will help others, in addition to solving my problems.
  • I have looked into alternative solutions to the best of my ability.
  • (optional) I would be willing to contribute to testing this feature if implemented, or making a PR to implement this functionality.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions