mardausdennis / reservationmoduledisapp24 Goto Github PK

In the CalendarPage class, a NullReferenceException occurs when the user selects a date from the calendar popup and clicks the confirmation button. This issue needs to be investigated and resolved to ensure proper functionality of the date selection process.

Steps to reproduce:

1. Open the app and navigate to the ReservationPage.
2. Click on the "Datum auswählen" button to open the calendar popup.
3. Select a date from the calendar.
4. Click the confirmation button.

Expected behavior:
The selected date should be displayed on the ReservationPage without any errors.

Actual behavior:
A System.NullReferenceException is thrown, indicating that an object reference is not set to an instance of an object.

Suggested fix:

Check the DisplaySelectedDates method in the CalendarPage.xaml.cs file and ensure that all objects are properly initialized and accessed.

Labels: bug, high-priority

Currently, on the Calendar Page in our app, the header displays "Navigated Date" instead of "Selected Date" when a user selects a date. This can be confusing for users and should be updated to show the correct information.

We need to update the code for the Calendar Page to correctly display the selected date in the header when a user chooses a date. This change will improve the user experience and make our app more intuitive.

To implement this change, we will need to update the code in the CalendarPage.xaml.cs file to modify the header label. We will also need to test the updated functionality to ensure it is working correctly.

When the content of the ContentPage is too long, it is not possible to scroll down and see the entire content. This happens even when the content is wrapped in a StackLayout. This is problematic because it makes it impossible to read the entire content for long articles or posts.

Steps to reproduce:

1. Create a ContentPage with a long content, for example, a long HTML text.
2. Navigate to the ContentPage.
3. Try to scroll down and read the entire content.

Expected behavior: The content should be scrollable, and it should be possible to read the entire content.

Actual behavior: The content is not scrollable, and it is not possible to read the entire content.

When clicking on an item in the RssFeedView, the detailed content page is displayed, but only the title and release date are shown, and not the actual content of the item. This makes it difficult for users to fully engage with the content and defeats the purpose of having a detailed content page. We need to fix this issue and ensure that the full content of the selected Rss item is displayed in the detailed content page.