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

chore(docs): fix typos #6865

Merged
merged 2 commits into from
Jan 16, 2025
Merged

chore(docs): fix typos #6865

merged 2 commits into from
Jan 16, 2025

Conversation

mkrl
Copy link
Contributor

@mkrl mkrl commented Jan 16, 2025

Description

Fixes a few typos I noticed while browsing the docs.

Type of change

Only doc annotations are altered, no functional code changes are included in this PR.

  • This change requires a documentation update

Screenshots/Sandbox (if appropriate/relevant):

The current version can be seen @ https://the-guild.dev/graphql/tools/docs/api/modules/mock_src#createmockstore

image

How Has This Been Tested?

I assume docs are automatically generated from annotations in the code. Let me know if there's anything else that should be changed.

Checklist:

  • I have followed the
    CONTRIBUTING doc and the
    style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests and linter rules pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules

Let me know if this semantic commit title works, I'm not 100% sure it's the correct convention for this repo.
Cheers!

Copy link

changeset-bot bot commented Jan 16, 2025

⚠️ No Changeset found

Latest commit: 5ed6eea

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

@ardatan
Copy link
Owner

ardatan commented Jan 16, 2025

Thanks! Could you create a changeset with yarn changeset? Then we can merge and release!

@mkrl
Copy link
Contributor Author

mkrl commented Jan 16, 2025

@ardatan my impression was that the changes to the doc annotations should not generate a new version (perhaps it can just be a part of the next release), but I've added the changeset just now.

Thanks!

@ardatan ardatan merged commit 309748d into ardatan:master Jan 16, 2025
16 checks passed
@ardatan
Copy link
Owner

ardatan commented Jan 16, 2025

It is still change in the code(TSDoc). So it is fine to release it in my opinion! Thanks!

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