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
Based on #1414 , one way to tackle the fragments issue is to allow the rename transform to rename multiple type into a single one - that will allow a manual process of renaming only the types that match and use fragments on the resulting type.
I saw regex can be used, but that might also affect unrelated types so Translations(.*) will affect Translations, TranslationsListListItem and TranslationsInput, while we only want to affect Translations, TranslationsListListItem .
type Query {
# get translations
#
# Equivalent to GET /translations/{translation_id}
getTranslationById(translationId: String): Translation
# get translations list
#
# Equivalent to GET /translations/list
getTranslationsList(
# Auto-generated argument that limits the size of returned list of objects/list, selecting the first `n` elements of the list
limit: Int
): [Translation]
}
type Translation {
displayName: DisplayName
id: String
key: String
platform: [String]
title: String
}
type DisplayName {
en: String
he: String
}
Another issue, is that currently it is not possible to rename into an existing type, but the above should basically allow to rename TranslationsListListItem to Translation even though it exists.
The text was updated successfully, but these errors were encountered:
Based on #1414 , one way to tackle the fragments issue is to allow the rename transform to rename multiple type into a single one - that will allow a manual process of renaming only the types that match and use fragments on the resulting type.
I saw regex can be used, but that might also affect unrelated types so Translations(.*) will affect
Translations
,TranslationsListListItem
andTranslationsInput
, while we only want to affectTranslations
,TranslationsListListItem
.So the SDL in #1414 could rename be presented as:
Another issue, is that currently it is not possible to rename into an existing type, but the above should basically allow to rename
TranslationsListListItem
toTranslation
even though it exists.The text was updated successfully, but these errors were encountered: