Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Translate current mapping transformations when expression is enabled

See original GitHub issue

Pre Condition:

Have source fields firlstName and lastName
Both of source fields have Capitalize transformation
many-to-one transoformation Concatenate is selected with a delimiter (white space)

Expected default expression when expression is enabled: Concatenate(Capitalize(/path/to/firstName), Capitalize(/path/to/lastName), ' ')

We could add a REST endpoint that translates a mapping into expression, if not appropriate to calculate in UI directly.

Issue Analytics

State:
Created 3 years ago
Comments:6 (2 by maintainers)

Top GitHub Comments

1reaction

pleacucommented, Nov 24, 2020

Hey @igarashitm - I’ve got most of the infrastructure set up to send the mappings down to the runtime service to have them translated but I’m now thinking it’s a lot of work and time. I’m now thinking it’s really not a big deal to just have the UI create the expression from the mappings. Will go that route.

0reactions

igarashitmcommented, Dec 3, 2020

It would be null instead of empty string to reflect original behavior.