Implementing an additional option to retrieve all properties except specific ones #4460
AbdlrahmanSaberAbdo
started this conversation in
Ideas
Replies: 1 comment
-
I'd call it just exclude. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Referring to the discussion found at #2984, I would like to introduce a new functionality that, to the best of my knowledge, has not been implemented yet.
My idea is to create an option called
allFieldsWithout
orfieldsWithout
. To get started with the code base, I examined how the existingfields
option is implemented. I noticed that thebuildFields
method is used in the following classes:To begin implementing this option, I plan to first add it to the
findOptions
interface. Now, my question is whether I should implement theexclude
method in each of these classes. My approach would involve excluding the specified property from the metadata'sprops
and then including all other properties. Should this functionality also support excluding fields from relations? Initially, I'd like to focus on excluding props specific to the specified entity/table.Additionally, I believe it's necessary to impose some restrictions to prevent the user from specifying both options (
fields
andfieldsWithout
) simultaneously. What are your thoughts on this?Before proceeding, I'd like to make sure that you're welcome with this option, @B4nan. It would also be greatly appreciated if you could provide some guidance to help me get started.
Beta Was this translation helpful? Give feedback.
All reactions