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

remove transform style warning since the native alternative doesn't work for most cases. #2622

Conversation

EvanBacon
Copy link
Contributor

The string interpolation system doesn't appear to work with React Animated as the string would convert the animated object to [Object object].

Copy link

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 546b147:

Sandbox Source
react-native-web-examples Configuration

@necolas
Copy link
Owner

necolas commented Dec 20, 2023

Re: interpolation #2528 (comment)

@necolas necolas closed this in 24212aa Dec 20, 2023
@EvanBacon EvanBacon deleted the @evanbacon/remove-transform-style-warning branch December 20, 2023 22:01
EvanBacon added a commit to expo/expo that referenced this pull request Feb 1, 2024
…SSR (#26812)

# Why

It's too hard to make sense of the console logs that are executed in the
server renderer. This PR aims to add more clarity.

<img width="906" alt="Screenshot 2024-01-30 at 8 56 19 PM"
src="https://github.com/expo/expo/assets/9664363/3ab0d3e5-9d71-4bc5-a7fe-3691472cc73d">

We'll now add the same log tagging as logs that come from native
clients. However, we'll also add a lambda character to indicate that the
log is from a server platform (we should do this disambiguation for
every platform imo).

If the log is of type warn or error, then we'll also show a formatted
stack trace with hidden files removed unless `EXPO_DEBUG` is enabled.

You can see from the screenshot above that the pesky warnings are coming
from react navigation and safe area context. Every user will see these
warnings in every project, so we should aim to resolve the warnings.

- safe area context warning is fixed here
th3rdwave/react-native-safe-area-context@e2c8027
- react navigation warnings fixed here
necolas/react-native-web#2622
- error is just an example in the app source. In production, this will
only show the last trace.

---------

Co-authored-by: Expo Bot <[email protected]>
EvanBacon added a commit to expo/expo that referenced this pull request Feb 1, 2024
…SSR (#26812)

It's too hard to make sense of the console logs that are executed in the
server renderer. This PR aims to add more clarity.

<img width="906" alt="Screenshot 2024-01-30 at 8 56 19 PM"
src="https://github.com/expo/expo/assets/9664363/3ab0d3e5-9d71-4bc5-a7fe-3691472cc73d">

We'll now add the same log tagging as logs that come from native
clients. However, we'll also add a lambda character to indicate that the
log is from a server platform (we should do this disambiguation for
every platform imo).

If the log is of type warn or error, then we'll also show a formatted
stack trace with hidden files removed unless `EXPO_DEBUG` is enabled.

You can see from the screenshot above that the pesky warnings are coming
from react navigation and safe area context. Every user will see these
warnings in every project, so we should aim to resolve the warnings.

- safe area context warning is fixed here
th3rdwave/react-native-safe-area-context@e2c8027
- react navigation warnings fixed here
necolas/react-native-web#2622
- error is just an example in the app source. In production, this will
only show the last trace.

---------

Co-authored-by: Expo Bot <[email protected]>
gypaullin pushed a commit to Cofit/react-native-web that referenced this pull request Jul 5, 2024
React Native's implementation of string transforms is incomplete.

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

Successfully merging this pull request may close these issues.

2 participants