handling modularized API-URL string bank in ASP.net [7:30am]

[frankcollins3]

attempting to do: make a reference of this below seen url string for http requests elsewhere, and import in this code.

in react/nextJS: one could put these in a utility/url.ts folder or even encapsulate the application with an app.tsx level that delivers typesafe, valuedefined useContext()

error: no error yet

proposed approach: /Data/string.cs (use a namespace)?

possible improvements:

[frankcollins3]

this is what chatGPT had to say about it:

here's why I find their response confusing. take this invocation of the public class: var apiUrls = new ApiUrls();

// we don't do such a thing for the Model and Controller: [7:49am]

[frankcollins3]

{insert-tabloidy:"You wont belive what they said!" type of headline} [7:51am]

// sidenote.. before chat responded that was my next question. are classes variables? I guessed that they were objects & it's the reason why I avoided usage of "variable" in the above comment. [7:52am]

[frankcollins3]

// sidenote: chat redeeming themselves after taking 3 days to set up EF when stack overflow helped in 30 mins lol. [7:53am]

[frankcollins3]

namespace and public class it is. now having a separate issue with namespace definition and referenceability [8:07am]

[frankcollins3]

[8:09am]

[frankcollins3]

but then try this and get this output:

[8:10am]