Skip to content

fix: correct type error as a result of removed imports #2854

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

Open
wants to merge 12 commits into
base: master
Choose a base branch
from

Conversation

ifeanyi-ugwu
Copy link
Contributor

🚨 IMPORTANT: Please do not create a Pull Request without creating an issue first.

Any change needs to be discussed before proceeding. Failure to do so may result in the rejection of
the pull request.

Description

Please include a summary of the change and which issue is fixed. Please also include relevant
motivation and context. List any dependencies that are required for this change.

Related # (issue)

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as
    expected)
  • This change requires a documentation update

Screenshots/Sandbox (if appropriate/relevant):

Adding links to sandbox or providing screenshots can help us understand more about this PR and take
action on it as appropriate

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can
reproduce. Please also list any relevant details for your test configuration

  • Test A
  • Test B

Test Environment:

  • OS:
  • GraphQL Scalars Version:
  • NodeJS:

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

Further comments

If this is a relatively large or complex change, kick off the discussion by explaining why you chose
the solution you did and what alternatives you considered, etc...

- Added .mdx documentation for scalar types: GUID, HSLA, ISO8601Duration, LCCSubclass, Long, SESSN, UnsignedFloat, and UnsignedInt.
- Resolves issue graphql-hive#2019 regarding missing scalar type documentation.
- Introduced a custom GeoJSON scalar type.
- Added unit tests to ensure proper validation and functionality of the GeoJSON scalar.
- Updated documentation website to reflect the new scalar type and usage.
- Resolves issue graphql-hive#2061.
- Updated GeoJSON imports to use .js extensions, resolving import errors in tests.
- Removed index.ts re-export of GeoJSON to reduce bundle size by approximately 4KB.
- Eliminated the codegenScalarType generate function, saving an additional ~8KB.
- Revised GeoJSON documentation to clarify its integration with GraphQL Codegen.
- Saved ~3kb by removing the geojsonSchema from the extensions of the GeoJSON scalar.
- Updated documentation to reflect the change in how the GeoJSON's json schema is accessed.
…en type

- Switched validation from regex to Set lookup for performance and clarity
- Tests now source from COUNTRY_CODES enum directly, ensuring full coverage
- codegenScalarType now emits explicit union of allowed values instead of generic `string`
- Switched validation from regex to Set lookup for performance and clarity
- Tests now source from CURRENCY_CODES enum directly, ensuring full coverage
- codegenScalarType now emits explicit union of allowed values instead of generic `string`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant