Update Posyandu, JadwalPosyandu, and Pemeriksaan

[itsLeonB]

Summary by CodeRabbit

• New Features

  • Introduced a new search functionality with a search bar for improved navigation.
  • Added a date and time picker to streamline the scheduling process.
  • Implemented new floating action buttons for enhanced user interaction.

• Enhancements

  • Improved fragment transition effects for a smoother user experience.
  • Refined back button behavior in various fragments for intuitive navigation.

• Bug Fixes

  • Adjusted timestamp issue in deployment settings for accurate scheduling.

• Refactor

  • Streamlined dialog creation and handling to improve maintainability.
  • Optimized button click handling within fragments for better performance.

• Style

  • Updated UI elements for a more cohesive visual experience.

• Documentation

  • Enhanced code annotations for better clarity and future maintenance.

[coderabbitai]

Walkthrough

The updates reflect a series of enhancements and refactoring across various Kotlin files in an Android app. Timestamps were updated, user interfaces were streamlined by replacing extended floating action buttons with regular ones, and improved dialog management. Snackbar imports suggest an increase in user feedback mechanisms. Fragment transactions now include transitions and are added to the back stack for better navigation. New fragments for creating and viewing Pemeriksaan, as well as editing Posyandu details, enhance the app's functionality.

Changes

File Path	Change Summary
.idea/deploymentTargetDropDown.xml	Updated the timeTargetWasSelectedWithDropDown timestamp.
.../JadwalPosyanduFragment.kt	UI components updated, dialog functions renamed, added button handling, and refactored date/time picker.
.../MainActivity.kt	Enhanced fragment transaction with transition effects and back stack management.
.../PemeriksaanCreateFragment.kt .../PemeriksaanViewFragment.kt .../PosyanduEditFragment.kt	Introduced new fragments with lifecycle methods for creation, viewing, and editing.
.../PosyanduFragment.kt	Added new methods for menu and dialog management, and updated button handling.

🐇✨
A hop of code, a leap of design,
Buttons and fragments, all now align.
With each commit, the app does refine,
CodeRabbit's joy, in each new line. 🌟📱

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on X ?

---

Tips

Chat with CodeRabbit Bot (@coderabbitai)

• You can reply to a review comment made by CodeRabbit.
• You can tag CodeRabbit on specific lines of code or files in the PR by tagging @coderabbitai in a comment.
• You can tag @coderabbitai in a PR comment and ask one-off questions about the PR and the codebase. Use quoted replies to pass the context for follow-up questions.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

[coderabbitai]

Review Status

Actionable comments generated: 2

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between b3305ab and b33026c.

Files ignored due to filter (38)

• app/src/androidTest/res/drawable/close.xml
• app/src/main/AndroidManifest.xml
• app/src/main/res/color/bottom_nav_icon_color_selector.xml
• app/src/main/res/color/chip.xml
• app/src/main/res/color/segmented_button.xml
• app/src/main/res/drawable/check.xml
• app/src/main/res/drawable/ic_plus.xml
• app/src/main/res/drawable/settings.xml
• app/src/main/res/drawable/swap.xml
• app/src/main/res/drawable/warning.xml
• app/src/main/res/drawable/warning_sign.xml
• app/src/main/res/layout/activity_login.xml
• app/src/main/res/layout/activity_lupa.xml
• app/src/main/res/layout/activity_main.xml
• app/src/main/res/layout/activity_sandi_baru.xml
• app/src/main/res/layout/activity_verifikasi_reset.xml
• app/src/main/res/layout/fragment_home.xml
• app/src/main/res/layout/fragment_jadwal_konsultasi.xml
• app/src/main/res/layout/fragment_jadwal_konsultasi_bidan.xml
• app/src/main/res/layout/fragment_jadwal_posyandu.xml
• app/src/main/res/layout/fragment_jadwal_posyandu_create.xml
• app/src/main/res/layout/fragment_jadwal_posyandu_edit.xml
• app/src/main/res/layout/fragment_jadwal_posyandu_view.xml
• app/src/main/res/layout/fragment_konsultasi.xml
• app/src/main/res/layout/fragment_materi.xml
• app/src/main/res/layout/fragment_pemeriksaan_create.xml
• app/src/main/res/layout/fragment_pemeriksaan_view.xml
• app/src/main/res/layout/fragment_posyandu.xml
• app/src/main/res/layout/fragment_posyandu_bidan.xml
• app/src/main/res/layout/fragment_posyandu_edit.xml
• app/src/main/res/layout/fragment_posyandu_kader.xml
• app/src/main/res/layout/fragment_posyandu_remaja.xml
• app/src/main/res/layout/fragment_profile.xml
• app/src/main/res/menu/posyandu_settings_menu.xml
• app/src/main/res/values/arrays.xml
• app/src/main/res/values/colors.xml
• app/src/main/res/values/styles.xml
• app/src/main/res/values/themes.xml

Files selected for processing (7)

• .idea/deploymentTargetDropDown.xml (1 hunks)
• app/src/main/java/com/example/posyandu/JadwalPosyanduFragment.kt (6 hunks)
• app/src/main/java/com/example/posyandu/MainActivity.kt (2 hunks)
• app/src/main/java/com/example/posyandu/PemeriksaanCreateFragment.kt (1 hunks)
• app/src/main/java/com/example/posyandu/PemeriksaanViewFragment.kt (1 hunks)
• app/src/main/java/com/example/posyandu/PosyanduEditFragment.kt (1 hunks)
• app/src/main/java/com/example/posyandu/PosyanduFragment.kt (2 hunks)

Files skipped from review due to trivial changes (1)

• .idea/deploymentTargetDropDown.xml

Additional comments: 13

app/src/main/java/com/example/posyandu/JadwalPosyanduFragment.kt (2)

• 39-43: The btnTambah click listener only calls showCreateDialog(). If this dialog is responsible for creating a new schedule, consider validating the input data before proceeding with the creation process to ensure data integrity.

• 192-197: The @SuppressLint("NewApi") annotation is used, which suggests that newer API features are being used without proper API level checks. Ensure that there are runtime checks to prevent MaterialDatePicker from causing crashes on older Android versions that do not support it.

app/src/main/java/com/example/posyandu/MainActivity.kt (2)

• 6-6: The import androidx.fragment.app.FragmentTransaction is added to support enhanced fragment transaction logic. Ensure that all fragment transactions in the app are updated to use these new methods for consistency.

• 50-57: The fragment transaction logic has been updated to include transitions and back stack management. Verify that this change does not introduce any regressions in the navigation flow, such as unexpected behavior when the back button is pressed.

app/src/main/java/com/example/posyandu/PemeriksaanCreateFragment.kt (2)

• 17-23: The back press callback is overridden to pop the back stack. Ensure that this behavior is consistent with the user's expectation across the app, and there are no fragments where the back press should have a different behavior.

• 45-62: The btnTambah click listener performs a fragment transaction and shows a Snackbar. Ensure that the transaction is committed after the data has been successfully saved to prevent misleading the user with the success message.

app/src/main/java/com/example/posyandu/PemeriksaanViewFragment.kt (1)

• 13-19: Similar to PemeriksaanCreateFragment, verify that the back press behavior is consistent and expected across the app.

app/src/main/java/com/example/posyandu/PosyanduEditFragment.kt (2)

• 20-24: The back press callback is overridden to pop the back stack. Consistency in navigation behavior should be checked across all fragments.

• 41-51: The btnSimpan click listener updates the fragment and shows a Snackbar. Ensure that the update operation is completed successfully before showing the success message.

app/src/main/java/com/example/posyandu/PosyanduFragment.kt (4)

• 3-25: Multiple new imports are added. Verify that all of them are used in the file and remove any that are not necessary to avoid cluttering the codebase.

• 57-68: The cardJadwalPosyandu click listener now includes a fragment transaction with a transition and back stack management. Ensure that this new behavior is tested for consistency with the rest of the app's navigation.

• 80-100: The showMenu function uses a PopupMenu to display options. Ensure that the menu items are correctly handled and that the user experience is consistent with the rest of the app.

• 103-120: The showPosyanduDialog function presents a dialog with options. Verify that the selection of these options leads to the correct behavior and that the state of the app is updated accordingly.

[mauritzmauritz]

gg jon ajarin lah