Skip to content

fix: unnests the user id in the regex suite#113

Merged
sighphyre merged 5 commits intomainfrom
fix/property-mapping-in-regex-suite
Feb 25, 2026
Merged

fix: unnests the user id in the regex suite#113
sighphyre merged 5 commits intomainfrom
fix/property-mapping-in-regex-suite

Conversation

@sighphyre
Copy link
Member

This isn't actually a valid context structure. Top level properties belong in the top layer. This is tolerated in the Node SDK because JavaScript reasons . It's tolerated in Yggdasil because Edge (backed by Yggdasil) needs to match the frontend API (backed by the Node SDK). Sooo... also because JavaScript reasons

This unnests that structure so literally every single other SDK we have can actually use this

}
]
},
{
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tests for this project assert that top level props can't be explicitly null so we work around that by offloading it to a property

@github-project-automation github-project-automation bot moved this from New to Approved PRs in Issues and PRs Feb 25, 2026
@sighphyre sighphyre merged commit b90913f into main Feb 25, 2026
1 check passed
@github-project-automation github-project-automation bot moved this from Approved PRs to Done in Issues and PRs Feb 25, 2026
@sighphyre sighphyre deleted the fix/property-mapping-in-regex-suite branch February 25, 2026 12:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

3 participants