Feat/update add task screen

[CroyzCamel]

Issue

This pull request refers to Issue #

• Does not apply to this pull request

Description

Please include a summary of the change and which issue is fixed.

Types of changes

• New feature (non-breaking change which adds functionality).
• [x} Bug fix (non-breaking change which fixes an issue).
• Breaking change (fix or feature that would cause existing functionality to not work as expected).

What changed:

• UI
• Business rule
• Documentation
• Gradle or Build
• Navigation
• Tests
• Resource files
• Project architecture
• Code style

Checklist

• Have tested the changes.
• Met all the acceptance requirements of this task.
• Verified if branch is up-to-date with develop (if not - rebase it or merge it).
• Resolve git conflicts

If any of the acceptance criteria are not met, please explain why below

What is the criteria? Why it is different?

[Copilot]

Copilot reviewed 34 out of 34 changed files in this pull request and generated 1 comment.

Comments suppressed due to low confidence (3)

app/src/main/java/com/routinely/routinely/task/EditTaskScreen.kt:134

• Ensure that initialTask.date always follows the 'yyyy-MM-dd HH:mm' format to prevent potential runtime parsing errors.

val dateTime = LocalDate.parse(initialTask.date, dateTimeFormatter)

app/src/main/java/com/routinely/routinely/home/HomeScreen.kt:68

• [nitpick] Consider removing the unused variable 'temporaryDeleteId' to clean up dead code if it is not required.

val temporaryDeleteId by remember { mutableStateOf<TaskItem?>(null) }

app/src/main/java/com/routinely/routinely/task/AddTaskScreen.kt:234

• Consider enforcing validation on taskDate and taskTime so that formattedDate is not an empty string, which could lead to API errors.

val formattedDate = if (taskDate.isNotEmpty() && taskTime.isNotEmpty()) { "$taskDate $taskTime" } else { "" }

[Copilot]

[nitpick] Replace the println statement with a proper logging mechanism (e.g. Timber) to ensure consistent and production-ready error logging.

Suggested change

	println("Erro ao processar resposta: ${e.message}")
	Timber.e(e, "Erro ao processar resposta")

[OdisBy]

Eu ia falar isso, mas ele falou antes kkkk. Tbm recomendo usar o Timber, talvez o Timber.d e continuar a msg + o erro como estava antes ou como ele recomendou, vc que sabe.

[MarcosNazario]

Teste realizado, permitindo navegar pelas telas de criação de atividade, seja "Tarefa" ou "Hábito", porém não possíbilita a conclusão da jornada. Ao tentar finalizar a jornada, clicando em "Adicionar tarefa", é exibida mensagem de erro, seguem abaixo as evidências: