You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
If there are 2 versions of the @exogee/graphweaver package resolvable, then there is a good chance that any metadata populated will not make it into the generated schema. This is because the user might be importing version X, but the metadata object attached the Graphweaver version Y is the one resolved by the app itself, which will be default / empty.
To Reproduce
Steps to reproduce the behavior:
You should be able to reproduce the issue by installing a mix of packages for the Graphweaver ecosystem, for example 2.9.1 vs 2.8.2
Expected behavior
The app should detect this might be the cause and provide some feedback to the user or fail.
Actual behavior
The app starts up fine, but no extra mutations etc are available
Screenshots or Screencasts
If applicable, add screenshots or screencasts to help explain the issue.
Desktop (please complete the following information):
OS and version: [e.g. MacOS 13.3.1, Windows 11 v22H2]
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
eddiesholl
changed the title
Metadata does not make it into generated schema if 2 versions of Graphweaver are installed / in scope
Metadata does not make it into generated schema if multiple versions of Graphweaver are installed / in scope
Dec 4, 2024
Describe the bug
If there are 2 versions of the @exogee/graphweaver package resolvable, then there is a good chance that any metadata populated will not make it into the generated schema. This is because the user might be importing version X, but the metadata object attached the Graphweaver version Y is the one resolved by the app itself, which will be default / empty.
To Reproduce
Steps to reproduce the behavior:
You should be able to reproduce the issue by installing a mix of packages for the Graphweaver ecosystem, for example 2.9.1 vs 2.8.2
Expected behavior
The app should detect this might be the cause and provide some feedback to the user or fail.
Actual behavior
The app starts up fine, but no extra mutations etc are available
Screenshots or Screencasts
If applicable, add screenshots or screencasts to help explain the issue.
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: