Dev#19
Closed
fdhliakbar wants to merge 13 commits into
Closed
Conversation
feat: fetch superadmin & crete table vehicle with model
* feat: handle edit vehicle function * fix: axios error when editing vehicle Things that I changed : - change all year data types into number, cuz in the backend, it required as number, not a string. - Change the selected value text in the edit form exactly like vehicleType. Because if the text is not the same, then the item cannot be selected. * feat: add handle delete vehicle function
* feat: handle edit vehicle function * fix: axios error when editing vehicle Things that I changed : - change all year data types into number, cuz in the backend, it required as number, not a string. - Change the selected value text in the edit form exactly like vehicleType. Because if the text is not the same, then the item cannot be selected. * feat: add handle delete vehicle function * feat: implement vehicle management features including model retrieval and vehicle addition * fix: tsconfig.app.json --------- Co-authored-by: rendybp <rendibuanap@gmail.com>
* feat: handle edit vehicle function * fix: axios error when editing vehicle Things that I changed : - change all year data types into number, cuz in the backend, it required as number, not a string. - Change the selected value text in the edit form exactly like vehicleType. Because if the text is not the same, then the item cannot be selected. * feat: add handle delete vehicle function * feat: implement vehicle management features including model retrieval and vehicle addition * fix: tsconfig.app.json * fix: login and private route validation for super_admin role --------- Co-authored-by: rendybp <rendibuanap@gmail.com>
* Dev (#6) * feat: fetch superadmin & crete table vehicle with model * Rendi/company management logic (#3) * feat: handle edit vehicle function * fix: axios error when editing vehicle Things that I changed : - change all year data types into number, cuz in the backend, it required as number, not a string. - Change the selected value text in the edit form exactly like vehicleType. Because if the text is not the same, then the item cannot be selected. * feat: add handle delete vehicle function * Fadhli/create vehicle for integration mx (#4) * feat: handle edit vehicle function * fix: axios error when editing vehicle Things that I changed : - change all year data types into number, cuz in the backend, it required as number, not a string. - Change the selected value text in the edit form exactly like vehicleType. Because if the text is not the same, then the item cannot be selected. * feat: add handle delete vehicle function * feat: implement vehicle management features including model retrieval and vehicle addition * fix: tsconfig.app.json --------- Co-authored-by: rendybp <rendibuanap@gmail.com> --------- Co-authored-by: Rendy Buana Perdana <52504900+rendybp@users.noreply.github.com> Co-authored-by: rendybp <rendibuanap@gmail.com> * Dev (#9) * feat: fetch superadmin & crete table vehicle with model * Rendi/company management logic (#3) * feat: handle edit vehicle function * fix: axios error when editing vehicle Things that I changed : - change all year data types into number, cuz in the backend, it required as number, not a string. - Change the selected value text in the edit form exactly like vehicleType. Because if the text is not the same, then the item cannot be selected. * feat: add handle delete vehicle function * Fadhli/create vehicle for integration mx (#4) * feat: handle edit vehicle function * fix: axios error when editing vehicle Things that I changed : - change all year data types into number, cuz in the backend, it required as number, not a string. - Change the selected value text in the edit form exactly like vehicleType. Because if the text is not the same, then the item cannot be selected. * feat: add handle delete vehicle function * feat: implement vehicle management features including model retrieval and vehicle addition * fix: tsconfig.app.json --------- Co-authored-by: rendybp <rendibuanap@gmail.com> * Fadhli/create vehicle for integration mx (#7) * feat: handle edit vehicle function * fix: axios error when editing vehicle Things that I changed : - change all year data types into number, cuz in the backend, it required as number, not a string. - Change the selected value text in the edit form exactly like vehicleType. Because if the text is not the same, then the item cannot be selected. * feat: add handle delete vehicle function * feat: implement vehicle management features including model retrieval and vehicle addition * fix: tsconfig.app.json * fix: login and private route validation for super_admin role --------- Co-authored-by: rendybp <rendibuanap@gmail.com> --------- Co-authored-by: Rendy Buana Perdana <52504900+rendybp@users.noreply.github.com> Co-authored-by: rendybp <rendibuanap@gmail.com> * fix: pop up location of the menu button on the vehicle list page Fixed the pop-up location of the menu button on the vehicle list page that overflowed when clicking the last item in the table. * feat: add handle click outside for action button menu in the list vehicle. This feature allows users to click outside the pop-up action menu to close it. * fix: missing description payload in the add vehicle. Adding a description to the add vehicle payload. Previously, this payload had not been added at all, so it was not sent. * fix: double handle add vehicle function that cause error In the list-kendaraan.tsx file, there is a handleAddVehicle function that sends data to the wrong API, causing the second error (sending data twice). I deleted this function and focused on the add vehicle function in the dialog-kendaran-tambah.tsx. * refactor: handle edit vehicle Refactoring the vehicle edit function by moving the edit function to dialog-kendaraan-edit.tsx, just like the add vehicle function. Hopefully, this will make the code cleaner, less confusing, and easier to maintain. --------- Co-authored-by: Fadhliakbar <104522615+fdhliakbar@users.noreply.github.com>
- Added API functions for device management including CRUD operations. - Created a DataTable component for displaying devices with pagination. - Introduced pagination controls for navigating through device lists. - Developed a dialog for adding new devices with form validation. - Enhanced the device model and vehicle interfaces in types. - Updated the Fuel Calibration and User Management pages with placeholders. - Refactored the Manajemen Device page to include search functionality and error handling.
* feat: implement device management API and UI components - Added API functions for device management including CRUD operations. - Created a DataTable component for displaying devices with pagination. - Introduced pagination controls for navigating through device lists. - Developed a dialog for adding new devices with form validation. - Enhanced the device model and vehicle interfaces in types. - Updated the Fuel Calibration and User Management pages with placeholders. - Refactored the Manajemen Device page to include search functionality and error handling. * fix: unclickable vehicle search input in add device modal Refactored the vehicle dropdown from `<Select>` to a Combobox (`<Popover>` + `<Command>`). This resolves the unclickable search input issue caused by the strict focus trap in Radix UI's Select component, allowing users to properly type and search license plates. * fix: vehicle data not showing in dropdown Refactored the vehicle fetching logic to resolve missing data. Replaced the `getLicensePlate` API (which requires a `companyId`) with the `getAllVehicle` API to directly fetch all vehicle data. * feat: add edit and delete dialogs for device management --------- Co-authored-by: rendybp <rendibuanap@gmail.com>
- Implemented device features API for CRUD operations. - Added device GSM API for managing GSM-related data. - Created device identifiers API for handling device identifiers. - Developed device model pinout API for managing pinouts. - Introduced device model API for managing device models. - Added remote starter API for vehicle control. - Enhanced vehicle API with fuel calibration endpoints. - Updated device management UI to include dialogs for adding devices and device types. - Integrated new APIs into the device management page for better functionality.
* feat: add tipe-device-table I added a “Tipe Device” table and then included it on the device management page. Here, I used a toggle—similar to the one on the vehicle page—to switch between the device table and the device type table. * feat: add edit and hapus device dialog * fix: wrong api endpoint value that cause 404 not found error * feat: updating dialog tipe device edit UI with pin settings functionality to match the dialog tipe device add content * fix: dialog tipe device hapus flow ensuring proper pinout cleanup * feat: updating dialog device edit UI replicated from the dialog device add. Layout that replicated : 1. Device — Name, Device Model (Select), Vehicle (Combobox) 2. Identifiers — IMEI input 3. GSM — SIM Number + Provider in 2-column grid 4. Features — Pinout select (dynamic based on selected Device Model) * fix: replaced single deleteDeviceApi call with a 5-step sequential deletion that match the relationship in the device table * feat: adding an additional form which is vehicle fuel calibration and remote starter toggle in dialog kendaraan tambah * fix: add logic to the dialog kendaraan edit for triggering the fuel calibration and remote starter functions * feat: add calibration and remote startet api * feat: add vehicle features API and integrate feature assignment in vehicle addition dialog --------- Co-authored-by: rendybp <rendibuanap@gmail.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.