You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, CSV tables are defined as in the following example:
lettable=CSVTable<Person>(
columns:[CSVColumn("ID", \.id),CSVColumn("Name", \.name),
// etc.
],
configuration:.default
)
This isn't great for situations where I might need a more dynamic approach to column inclusion. For example, only users with a certain level of access may have access to personally sensitive information and their CSVs shouldn't attempt to include those columns. Or, I may have a feature in the app that is governed by a feature flag, and columns should be omitted if that flag is not on.
Another approach would be to use a ResultBuilder-style syntax for building table definitions, say:
Currently, CSV tables are defined as in the following example:
This isn't great for situations where I might need a more dynamic approach to column inclusion. For example, only users with a certain level of access may have access to personally sensitive information and their CSVs shouldn't attempt to include those columns. Or, I may have a feature in the app that is governed by a feature flag, and columns should be omitted if that flag is not on.
Another approach would be to use a ResultBuilder-style syntax for building table definitions, say:
This might also allow for configuration to be broken up and implemented as modifiers:
The text was updated successfully, but these errors were encountered: