Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Repairing Updating Rows from within the Seeding Report #551

Merged

Conversation

FutzMonitor
Copy link
Collaborator

@FutzMonitor FutzMonitor commented Jul 22, 2022

Pull Request Description

Closes #544. This pull request aims to fix the updateRows() method located inside of the Seeding Report html page. These changes are accompanied by a more rigorous testing case for the editing functionality of the table so that future devs realize that changing the headers to the table breaks the function responsible for updating the rows.

This PR is NOT ready to be merged yet
Things that need to be completed prior to a proper review for merging:

  • Fix a bug where changing area and any of the quantities together result in a status code 422 where the area is left empty and breaks the entire table's ability to generate a report for any dates for the broken log.
  • Determine why the backend isn't updating inside of the Cypress test while Hoppscotch confirms that changes to the logs on the frontend are going through in the backend.
  • Add another test case or test for the editing functionality for Users because it's currently untested.

Licensing Certification

FarmData2 is a Free Cultural Work and all accepted contributions are licensed as described in the LICENSE.md file. This requires that the contributor holds the rights to do so. By submitting this pull request I certify that I satisfy the terms of the Developer Certificate of Origin for its contents.

…updated.

1. Cypress tests need to be added to more rigorously test this change
1. There's a bug where changing area and quantity is causing a 422 status code.
2. The Cypress test seems to not be updating the values. This has to seriosuly be investigated.
1. Fixed a bug where updating the quantity and the area at the same time would result in a 422 status code from the server.
2. FIxed a bug where editing date, crop, area, comments, or user alongside any of the quantities would not update the log on the frontend with the appropriate information.
3. Added the IDToAreaMap in order to fix an issue where area would be empty inside the report page when updating it alongside other quantities.
4. Still need to update/add Cypress test(s) to test these changes
1. Made sure that the log inside of the report is accurate to the backend
1. Unfinished currently because we have to create a direct seeding log and an asset for testing purposes and the asset is producing an error.
@FutzMonitor FutzMonitor marked this pull request as ready for review July 27, 2022 20:05
@FutzMonitor
Copy link
Collaborator Author

This PR is ready to be reviewed. I decided not to implement the createRecord() piece into the tests because I intend to write an issue to changes all logs that are being created the current way to use createRecord() instead.

@braughtg braughtg merged commit 23baeed into DickinsonCollege:main Jul 28, 2022
@FutzMonitor FutzMonitor deleted the updateSeedingReportLogs branch July 28, 2022 13:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Seeding Report: Logs Are Not Being Updated
2 participants