search

fenterbug / Boson.ClickUp.Net

0 stars 0 forks source link

As a consumer, I need to provide API keys to the library so that I can access my ClickUp account data. #2

Open fenterbug opened 1 year ago

fenterbug commented 1 year ago

As of right now, I have my API keys in a JSON file that's being ignored by git. (I don't want everybody and their dog hitting my account as they test.) But other developers need some way to provide their API information privately. And, eventually, someone will be consuming this library and they will need to provide their API keys. What's the best way to do that?

dochoss commented 1 year ago

Provided in the main class constructor? I can put together a quick implementation tomorrow, I think.

fenterbug commented 1 year ago

I've thought about that, as well as an appsettings.json file and a couple of other things. Which is the right way? I don't know. It's probably the constructor approach like you suggest. I say go for it. Get's me out of my analysis paralysis.

fenterbug commented 1 year ago

Of course, it might be influenced by whatever it takes for the OAuth authentication. (??)

dochoss commented 1 year ago

Depends on if you want it set at runtime or build time. To use the class in code, you'd want it available at runtime. I'll put together an implementation tomorrow and get things moving 😝

From: fenterbug @.> Sent: Saturday, March 11, 2023 6:48:52 PM To: fenterbug/Boson.ClickUp.Net @.> Cc: dochoss @.>; Comment @.> Subject: Re: [fenterbug/Boson.ClickUp.Net] As a consumer, I need to provide API keys to the library so that I can access my ClickUp account data. (Issue #2)

I've thought about that, as well as an appsettings.json file and a couple of other things. Which is the right way? I don't know. It's probably the constructor approach like you suggest. I say go for it. Get's me out of my analysis paralysis.

— Reply to this email directly, view it on GitHubhttps://github.com/fenterbug/Boson.ClickUp.Net/issues/2#issuecomment-1465060601, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEIIB2JPHWSUHNB63NVS6I3W3UMPJANCNFSM6AAAAAAVVS44PQ. You are receiving this because you commented.Message ID: @.***>