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
In the objects (at least) : I can't ignore custom directives in examples when some types are nested. It doesn't show in the first type codeblock (as expected) but it does show in the example (unexpected).
To Reproduce
Create the simple schema below, and run docusaurus graphql-to-doc && docusaurus build . You can go on the given object in the sidebar (e.g. Cat) and see the type/example.
Expected behavior
In the example I just gave (+ screenshots) we can see that even though the Person attribute doesn't show in the initial type definition, it does show in the example.
However, if the type isn't nested (that's the case for bankAccount, it works as expected as we don't see it in the example.
Screenshots
In any case, thank you very much for your plugin, which is really cool and saves a lot of time!
The text was updated successfully, but these errors were encountered:
Describe the bug
In the objects (at least) : I can't ignore custom directives in examples when some types are nested. It doesn't show in the first
type
codeblock (as expected) but it does show in the example (unexpected).To Reproduce
Create the simple schema below, and run
docusaurus graphql-to-doc && docusaurus build
. You can go on the given object in the sidebar (e.g. Cat) and see the type/example.Expected behavior
In the example I just gave (+ screenshots) we can see that even though the
Person
attribute doesn't show in the initial type definition, it does show in the example.However, if the type isn't nested (that's the case for
bankAccount
, it works as expected as we don't see it in the example.Screenshots
![image](https://private-user-images.githubusercontent.com/20990730/322422340-c72040c0-300a-4b36-9b52-a61e14acf10b.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTg4NTM2ODEsIm5iZiI6MTcxODg1MzM4MSwicGF0aCI6Ii8yMDk5MDczMC8zMjI0MjIzNDAtYzcyMDQwYzAtMzAwYS00YjM2LTliNTItYTYxZTE0YWNmMTBiLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA2MjAlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNjIwVDAzMTYyMVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTVjYzQ3MmY5ZTJkOTZjMWI4YmI3ZWFjZjMzZmFmZDczZTYxMjBmMGJlNzRjNDFhNTJhM2QwN2VjNzQ0MDMyYWMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.4lHkvxR63fgyi-Q9pHgg7vNxkkIwfjmESBIM8BLayA4)
In any case, thank you very much for your plugin, which is really cool and saves a lot of time!
The text was updated successfully, but these errors were encountered: