Lakhasly

The ViewDeleteRequestFragment is an Android Fragment which is utilized to display details of a budget request and delete it. It defines several TextView objects to display various details like budget ID, name, moment, and status.Within the onCreateView method, the fragment_view_delete_request layout is inflated, and UI objects are initialized using findViewById.Also, the onResume method populates the TextView fields with their respective budget information from a shared data source, e.g., PassData.budgetModel.This function copies the customer_id from shared preferences and, using the HttpConnection class, makes a delete request with the corresponding budget_id and customer_id.If the delete button is clicked, it will show a confirmation dialog via the createDeleteDialog() function.

The ViewDeleteRequestFragment is an Android Fragment which is utilized to display details of a budget request and delete it. It defines several TextView objects to display various details like budget ID, name, moment, and status. Within the onCreateView method, the fragment_view_delete_request layout is inflated, and UI objects are initialized using findViewById. The buttons btnDelete and btnBack are initialized along with click listeners as well. If the delete button is clicked, it will show a confirmation dialog via the createDeleteDialog() function. The dialog prompts the user with a warning message for confirmation to delete the request. If the user confirms, it will begin a coroutine on the main thread to call the deleteRequest() suspend function. This function copies the customer_id from shared preferences and, using the HttpConnection class, makes a delete request with the corresponding budget_id and customer_id. It then shows the result of the operation in a toast message, and the fragment is returned back. The btnBack is merely a plain pop of the fragment from the stack. Also, the onResume method populates the TextView fields with their respective budget information from a shared data source, e.g., PassData.budgetModel.
For an "approved" budget status, it makes the delete button unavailable, thereby preventing deletion of approved requests.
Overall, this fragment is responsible for showing, confirming, and safely deleting a user's budget request, enabling confirmation by the user and preventing deletion of completed items.