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

Appointments not showing in calendar #57

Closed
kenrazo opened this issue Mar 28, 2023 · 5 comments · Fixed by #60
Closed

Appointments not showing in calendar #57

kenrazo opened this issue Mar 28, 2023 · 5 comments · Fixed by #60

Comments

@kenrazo
Copy link

kenrazo commented Mar 28, 2023

I tried to set it up in docker and in visual studio. The app is running but the appointments are not showing in the calendar even though I created a new one.,

@Rahtgaz
Copy link
Contributor

Rahtgaz commented Apr 20, 2023

Same problem when setting up the development environment for Visual Studio as explained in the readme-md file.
The FrontDesk.Blazor client app shows a yellow banner with a java handled exception, and does not show the appointments calendar.

@ardalis
Copy link
Owner

ardalis commented Apr 20, 2023

I think there may be some timezone issues associated with the default seeded appointments. I'm not sure why anyone would be seeing java errors - there's no java anywhere in the application. Do you mean JavaScript?

@Rahtgaz
Copy link
Contributor

Rahtgaz commented Apr 20, 2023

Yeah. I mean JavaScript. Don't even ask... 👎

So, the issue should be resolved in #59 which replaces the invariant culture specifier with the current culture of the client.

EDIT: Cancelled PR. That wasn't enough to make it work.

@Rahtgaz
Copy link
Contributor

Rahtgaz commented Apr 20, 2023

What I don't understand is that InvariantCulture is definitely an error in there and needs to be fixed. The following throws an exception:

var foo = new DateTimeOffset(2030, 9, 23, 0, 0, 0, new TimeSpan(-4, 0, 0));
var bar = DateTimeOffset.Parse(foo.ToString(), CultureInfo.InvariantCulture);

But when I change it to current culture, I still get the unhandled exception even though the string being displayed is definitely in the format accepted by my current culture.
image

@Rahtgaz
Copy link
Contributor

Rahtgaz commented Apr 21, 2023

@kenrazo #60 should fix it for you.

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 a pull request may close this issue.

3 participants