Idea: rework resource dependent options

[macrozone]

options grew organically and currenlty contain (among others):

• ResourceViews, which was initially to create "virtual" resource, but can now be used to customize fragment for one and many queries
• customizeInputData, can be used to alter input data before beeing sent to the backend
• filters, can be used to create custom filters. They are currently global, and not dependent on resources, which is odd

all those options kindof are related to a specific resource, so we could consider to rework those into something like this:

type Options = {

  resources: ResourceOptions

...

}

type ResourceOptions = Record<string, ResourceOption> // whereas key is the resourceName

type ResourceOption = {
   backendResource?: string // defaults to the key. This can be altered for "virtual" resources
  fragments: { // to alter what data is fetched, 
     one: ...,
     many: ... 
  },
  customizeInputData: {
     create: ...,
     update: ...
  },
filters: ...
}

so basically group the options. That will make it a bit easier to think about further improvements and customizations and is more logical

[macrozone]

@knapeto What do you think?

[knapeto]

I like it! I've never used customization for input data but make sense to me. Thanks for briefing @macrozone

[macrozone]

I like it! I've never used customization for input data but make sense to me. Thanks for briefing @macrozone

i actually just used it as a workaround (i was not even aware that we have it), i'll write this in a new ticket, since you might also stumbled across this https://github.com/panter/ra-data-prisma/issues/129