Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Enhancement] more options for FieldRename #1407

Open
lucavenir opened this issue Mar 10, 2024 · 1 comment
Open

[Enhancement] more options for FieldRename #1407

lucavenir opened this issue Mar 10, 2024 · 1 comment

Comments

@lucavenir
Copy link

lucavenir commented Mar 10, 2024

Thank you for providing the FieldRename enum. It quickly helps for common conventions.

It's great, but some backends adopt some weird naming conventions. I recently had to interface my client towards a server that returns only lowercase json fields, e.g.

{
  "somevaluewithnocase": 9
}

The fact that this is even a thing is very much debatable, thus making this request kind-of low-priority, but I was wondering if we could add more options for FieldRename, like for this one, above.

One good and complete list might be the following from mason. As you can see, there, we're pretty much allowed to do anything (obviously, it's a completely different context, and indeed there's some overlap, but you get the general idea).
https://docs.brickhub.dev/brick-syntax#built-in-lambdas

@kevmoo
Copy link
Collaborator

kevmoo commented Aug 15, 2024

PRs welcome!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants