TEST 44 RESOLVED: Testing to create Direct Seeding Log in Seeding Input #174
Conversation
|
Title: Question Regarding Variable Limits Within The FarmData2 Database Summary: Does the FarmData2 code cover the possibility of excessive large numbers that go beyond the possible seeding inputs available to a farm based on existing resources? Would a fix that involves setting up a configuration of existing resources on a farm to determine lower and upper limits to these variables serve as a fix? More importantly, would this be a desired feature fix by the farmers that use this software? Description: The FarmData2 project is designed to assist farmers around the world to easily record and report on crop and livestock production within the context of small organic farming operations to save time and resources while doing so. Giving the intended variability throughout farms in terms of total land, amount of seedings, number of livestock, and other important figures, does the code within FarmData2 implement limitations of these variables. Essentially, does the code cover the overall logistics to prevent potential overestimates for variables such as rows/bed, bed feet, # of workers, or # of minutes/hours of labor? For example, would it be possible to instate a configuration of figures to serve as a maximum figure (minimum figure would be >= 0) for each of these variables for a particular user to prevent faulty/accidental logs being passed to the database? A possible solution I see to this question would be to implement limits within the JavaScript code to limit the range of numbers you can select for each variable, dependent on the configuration set by the particular user (similar to the lower and upper limits to Date. We then can do a similar cypress test to the one designed in this issue (seen in #174 ), where we can test if our log was successfully added to the database. This is something I was curious about while working on this issue and some other related issues, so I wanted to know if a solution such as this is possible, and more importantly, something that would be considered important in the eyes of the users. Of course, this problem is dependent on the possibility the user would use extremely high values that go beyond the limitations within a seeding input job, but I believe it is something that could be considered if deemed important by the developers or the farmers themselves. Thank you for your time! |
Pull Request Description
Closes: #44
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.