Eric Rozell

@saroup - not convinced we really need this, but we could potentially make the timestamp optional...

/azp run

Turns out this is likely more challenging than I originally thought. Seems for NLU at least, that we need a custom comparer specific to NLU results for each property (intent,...

Probably a better idea is to use a prioritized list of comparers with target jpath queries.

This issue is probably not needed. We can't effectively test ASR -> entity results unless we are testing an end-to-end system and the entities are fully disambiguated. The correct approach...

We should validate that this works as expected with a container deployment of LUIS.

This also blocks use of native animations in some scenarios for us as well.

Here's another repro for this: https://github.com/rozele/react-native-windows/tree/repro3460 Here's the "expected" behavior using the JS animation driver: https://user-images.githubusercontent.com/1106239/149194070-bfb66137-07c1-484d-97da-e00963d45c31.mp4 Here's the "actual" behavior using the composition native animation driver: https://user-images.githubusercontent.com/1106239/149194090-278cb9c9-ae1b-42bd-8aa2-3ab52f13a7eb.mp4 Notice the translateX...

Re-opening, as this is technically still a bug for the composition-based NativeAnimated implementation and the tick-based implementation is opt-in. For a temporary workaround use: ``` // Animated.timing is an example,...

@acoates-ms Out of curiosity, what is your plan for passing the runtime to C++ TurboModules? I expect core React Native modules to start using this runtime argument in CallInvoker to...