WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
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
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Currently a serializer inside a module will be output as a single type, eg
Nested::AlbumSerializerbecomes aNestedAlbum:types_from_serializers/spec/types_from_serializers/__snapshots__/interfaces_Nested__AlbumSerializer.snap
Lines 7 to 11 in b47ac0f
There's some support for putting types into namespaces: #9
Idea
Wondering if it make sense to add a
module_into_namespacesoption, that will instead use the module name(s) to generate the namespace:This makes it easier to import all types for a single module, and keeps the Ruby and TS more in sync.
Unanswered questions:
Beta Was this translation helpful? Give feedback.
All reactions