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.

Sign up for GitHub

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

Jump to bottom

fix: use # instead of private keyword #5625

Merged
merged 1 commit into from
Apr 10, 2024
Merged

fix: use # instead of private keyword #5625

merged 1 commit into from
Apr 10, 2024

Conversation

GiveMe-A-Name
Copy link
Member

Summary

Related Links

Checklist

  • I have added changeset via pnpm run change.
  • I have updated the documentation.
  • I have added tests to cover my changes.

@changeset-bot changeset-bot
Copy link

changeset-bot bot commented Apr 10, 2024

⚠️ No Changeset found

Latest commit: a607659

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

@GiveMe-A-Name GiveMe-A-Name changed the title fix: use # instance of private fix: use # instead of private keyword Apr 10, 2024
@yimingjfe yimingjfe merged commit 619b253 into feat-new-server Apr 10, 2024
1 check passed
@yimingjfe yimingjfe deleted the qixuan/feat-new-server branch April 10, 2024 09:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@yimingjfe yimingjfe yimingjfe approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@GiveMe-A-Name @yimingjfe