Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature/dotnet 8 #91

Merged
merged 13 commits into from
Dec 8, 2023
Merged

Feature/dotnet 8 #91

merged 13 commits into from
Dec 8, 2023

Conversation

grofit
Copy link
Collaborator

@grofit grofit commented Dec 8, 2023

Updated to .net 8 as well as updating dependencies to reflect this or just bumping to newer versions where applicable, also some streamlining of the contexts and how logging occurs in controllers.

grofit added 13 commits October 30, 2023 14:32
This will potentially change a bit but its a first stab at mapping out the high level stuff, and the oauth isnt working fully yet.
This hopefully wont cause too much of an impact to existing code, but given we may need idTokens and/or refreshTokens in other scenarios it makes sense to be more specific in the naming of the tokens.
The auth is not persisting for some reason though.
Problem is Google only allows implicit auth for non client secret scenarios, and that has no way to update token, so when the token expires there is nothing you can do other than get the user to re-login all over again.
This at least makes client id/secret something the user provides.
This allows you to access the chat via a window.
@grofit grofit merged commit 44e42f7 into main Dec 8, 2023
3 checks passed
@grofit grofit deleted the feature/dotnet-8 branch December 8, 2023 20:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant