Any way to infer the string name value of the defining property in Typescript?












0















I'm creating a GraphQL app, and I have a challenge in my GQL type definitions.



company: {
type: OTCompany,
astNode: fieldDefinitionAST(OTCompany.name, 'company', [authDirective()]),
description: 'The company the campaign belongs to',
},
createdBy: {
type: OTUser,
astNode: fieldDefinitionAST(OTUser.name, 'createdBy', [authDirective()]),
description: 'The user that created the campaign',
},


As you can see, I have a string value that is always exactly the same as the field that it belongs to, in the cases above company and createdBy . I can't think of any way to get this value automatically without maintaining these fairly fragile string values. Does anyone have any ideas?










share|improve this question




















  • 1





    Please try to avoid asking multiple question in the same question.

    – k0pernikus
    Nov 23 '18 at 10:50











  • You're right, removed the addon question

    – jhm
    Nov 23 '18 at 13:14
















0















I'm creating a GraphQL app, and I have a challenge in my GQL type definitions.



company: {
type: OTCompany,
astNode: fieldDefinitionAST(OTCompany.name, 'company', [authDirective()]),
description: 'The company the campaign belongs to',
},
createdBy: {
type: OTUser,
astNode: fieldDefinitionAST(OTUser.name, 'createdBy', [authDirective()]),
description: 'The user that created the campaign',
},


As you can see, I have a string value that is always exactly the same as the field that it belongs to, in the cases above company and createdBy . I can't think of any way to get this value automatically without maintaining these fairly fragile string values. Does anyone have any ideas?










share|improve this question




















  • 1





    Please try to avoid asking multiple question in the same question.

    – k0pernikus
    Nov 23 '18 at 10:50











  • You're right, removed the addon question

    – jhm
    Nov 23 '18 at 13:14














0












0








0








I'm creating a GraphQL app, and I have a challenge in my GQL type definitions.



company: {
type: OTCompany,
astNode: fieldDefinitionAST(OTCompany.name, 'company', [authDirective()]),
description: 'The company the campaign belongs to',
},
createdBy: {
type: OTUser,
astNode: fieldDefinitionAST(OTUser.name, 'createdBy', [authDirective()]),
description: 'The user that created the campaign',
},


As you can see, I have a string value that is always exactly the same as the field that it belongs to, in the cases above company and createdBy . I can't think of any way to get this value automatically without maintaining these fairly fragile string values. Does anyone have any ideas?










share|improve this question
















I'm creating a GraphQL app, and I have a challenge in my GQL type definitions.



company: {
type: OTCompany,
astNode: fieldDefinitionAST(OTCompany.name, 'company', [authDirective()]),
description: 'The company the campaign belongs to',
},
createdBy: {
type: OTUser,
astNode: fieldDefinitionAST(OTUser.name, 'createdBy', [authDirective()]),
description: 'The user that created the campaign',
},


As you can see, I have a string value that is always exactly the same as the field that it belongs to, in the cases above company and createdBy . I can't think of any way to get this value automatically without maintaining these fairly fragile string values. Does anyone have any ideas?







typescript






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 23 '18 at 13:13







jhm

















asked Nov 23 '18 at 10:43









jhmjhm

1,61211331




1,61211331








  • 1





    Please try to avoid asking multiple question in the same question.

    – k0pernikus
    Nov 23 '18 at 10:50











  • You're right, removed the addon question

    – jhm
    Nov 23 '18 at 13:14














  • 1





    Please try to avoid asking multiple question in the same question.

    – k0pernikus
    Nov 23 '18 at 10:50











  • You're right, removed the addon question

    – jhm
    Nov 23 '18 at 13:14








1




1





Please try to avoid asking multiple question in the same question.

– k0pernikus
Nov 23 '18 at 10:50





Please try to avoid asking multiple question in the same question.

– k0pernikus
Nov 23 '18 at 10:50













You're right, removed the addon question

– jhm
Nov 23 '18 at 13:14





You're right, removed the addon question

– jhm
Nov 23 '18 at 13:14












1 Answer
1






active

oldest

votes


















0














You can use literal types:



Type Field = "company" | "createdBy";


or enums.






share|improve this answer
























  • Sure, an enum or type would make it statically typed at least, but what I'm looking for is how to automatically infer it seeing as it's always the same as the property itlself. :)

    – jhm
    Nov 23 '18 at 13:13











  • @jhm That's only possible with some level of reflection and I don't recommend going down that route. It may appear that the property and the value have something in common, yet a property-name and a value are still very different things. I sense an attempt of doing a premature abstraction. My guess is that you ain't gonna need it.

    – k0pernikus
    Nov 23 '18 at 17:25











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53445153%2fany-way-to-infer-the-string-name-value-of-the-defining-property-in-typescript%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









0














You can use literal types:



Type Field = "company" | "createdBy";


or enums.






share|improve this answer
























  • Sure, an enum or type would make it statically typed at least, but what I'm looking for is how to automatically infer it seeing as it's always the same as the property itlself. :)

    – jhm
    Nov 23 '18 at 13:13











  • @jhm That's only possible with some level of reflection and I don't recommend going down that route. It may appear that the property and the value have something in common, yet a property-name and a value are still very different things. I sense an attempt of doing a premature abstraction. My guess is that you ain't gonna need it.

    – k0pernikus
    Nov 23 '18 at 17:25
















0














You can use literal types:



Type Field = "company" | "createdBy";


or enums.






share|improve this answer
























  • Sure, an enum or type would make it statically typed at least, but what I'm looking for is how to automatically infer it seeing as it's always the same as the property itlself. :)

    – jhm
    Nov 23 '18 at 13:13











  • @jhm That's only possible with some level of reflection and I don't recommend going down that route. It may appear that the property and the value have something in common, yet a property-name and a value are still very different things. I sense an attempt of doing a premature abstraction. My guess is that you ain't gonna need it.

    – k0pernikus
    Nov 23 '18 at 17:25














0












0








0







You can use literal types:



Type Field = "company" | "createdBy";


or enums.






share|improve this answer













You can use literal types:



Type Field = "company" | "createdBy";


or enums.







share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 23 '18 at 10:48









k0pernikusk0pernikus

17.6k23109191




17.6k23109191













  • Sure, an enum or type would make it statically typed at least, but what I'm looking for is how to automatically infer it seeing as it's always the same as the property itlself. :)

    – jhm
    Nov 23 '18 at 13:13











  • @jhm That's only possible with some level of reflection and I don't recommend going down that route. It may appear that the property and the value have something in common, yet a property-name and a value are still very different things. I sense an attempt of doing a premature abstraction. My guess is that you ain't gonna need it.

    – k0pernikus
    Nov 23 '18 at 17:25



















  • Sure, an enum or type would make it statically typed at least, but what I'm looking for is how to automatically infer it seeing as it's always the same as the property itlself. :)

    – jhm
    Nov 23 '18 at 13:13











  • @jhm That's only possible with some level of reflection and I don't recommend going down that route. It may appear that the property and the value have something in common, yet a property-name and a value are still very different things. I sense an attempt of doing a premature abstraction. My guess is that you ain't gonna need it.

    – k0pernikus
    Nov 23 '18 at 17:25

















Sure, an enum or type would make it statically typed at least, but what I'm looking for is how to automatically infer it seeing as it's always the same as the property itlself. :)

– jhm
Nov 23 '18 at 13:13





Sure, an enum or type would make it statically typed at least, but what I'm looking for is how to automatically infer it seeing as it's always the same as the property itlself. :)

– jhm
Nov 23 '18 at 13:13













@jhm That's only possible with some level of reflection and I don't recommend going down that route. It may appear that the property and the value have something in common, yet a property-name and a value are still very different things. I sense an attempt of doing a premature abstraction. My guess is that you ain't gonna need it.

– k0pernikus
Nov 23 '18 at 17:25





@jhm That's only possible with some level of reflection and I don't recommend going down that route. It may appear that the property and the value have something in common, yet a property-name and a value are still very different things. I sense an attempt of doing a premature abstraction. My guess is that you ain't gonna need it.

– k0pernikus
Nov 23 '18 at 17:25


















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53445153%2fany-way-to-infer-the-string-name-value-of-the-defining-property-in-typescript%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Berounka

Sphinx de Gizeh

Different font size/position of beamer's navigation symbols template's content depending on regular/plain...