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

tokens: use Symbols instead of strings #595

Closed
wants to merge 1 commit into from

Conversation

alxndrsn
Copy link
Contributor

@alxndrsn alxndrsn commented May 8, 2024

No description provided.

Copy link

changeset-bot bot commented May 8, 2024

⚠️ No Changeset found

Latest commit: 49bf082

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@gajus
Copy link
Owner

gajus commented May 8, 2024

I am not against, but can you provide reasoning for why/how this is better?

@gajus
Copy link
Owner

gajus commented May 8, 2024

Separately, this highlights issue with the current test suite, as this would definitely break the slonik-sql-tag-raw package.

@mmkal
Copy link
Contributor

mmkal commented May 8, 2024

This will likely also cause problems for anyone trying to bundle slonik with esbuild, swc, webpack, turbopack, bun, parcel, ncc, etc. etc.

@gajus
Copy link
Owner

gajus commented May 8, 2024

This will likely also cause problems for anyone trying to bundle slonik with esbuild, swc, webpack, turbopack, bun, parcel, ncc, etc. etc.

aligned. I've seen this also cause issues when multiple versions of Slonik are loaded.

I can see why this could be desirable, but also cautious about how it would need to be implemented.

@alxndrsn
Copy link
Contributor Author

alxndrsn commented May 9, 2024

this would definitely break the slonik-sql-tag-raw package.

This will likely also cause problems for anyone trying to bundle slonik...

I've seen this also cause issues when multiple versions of Slonik are loaded.

@gajus @mmkal can you expand on likely issues? I can see how all of these things could be problematic if using the Symbol() constructor, but not with Symbol.for().

@github-actions github-actions bot mentioned this pull request May 9, 2024
@gajus
Copy link
Owner

gajus commented May 9, 2024

@gajus @mmkal can you expand on likely issues? I can see how all of these things could be problematic if using the Symbol() constructor, but not with Symbol.for().

My oversight. I was not familiar with Symbol.for().

This has now been released https://github.com/gajus/slonik/releases/tag/%40slonik%2Futilities%4044.0.0

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.

3 participants