docs: update stylex.defaultMarker usage to properly invoke it
#1267
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pawelblaszczyk5
requested review from
Jta26,
ezzak,
mellyeliu,
necolas,
nmn and
vincentriemer
as code owners
meta-cla
bot
added
the
CLA Signed
mellyeliu
pushed a commit
that referenced
this pull request
Oct 21, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changed / motivation ?
While migrating to newer version and using
stylex.defaultMarkerI spotted that it must be invoked. In opposite to the release blog post, where it's just passed in.Linked PR/Issues
N/A
Additional Context
TypeScript complaining it's a function:
I also verified and it correctly works when invoking + tests assume this, so the blog post has a small mistake here.
Pre-flight checklist
Contribution Guidelines