Added a field "Scientific Name" for more accurate plant care. #598
Conversation
This file contains 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
|
Added more fields and their choices to keep the plant health more targeted |
|
Looks good for me! Thanks for your contribution |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Many plants share common names but require very different care. For example, “Jade plant” could refer to a succulent Crassula ovata or Portulacaria afra, which have similar appearances but slightly different care needs.
Using scientific names eliminates ambiguity, ensuring that care routines are tailored to the exact species.
Scientific names can help pull in precise care guidelines from plant databases or care resources that catalog information based on species. This might include watering needs, optimal light exposure, soil preferences, and susceptibility to specific pests.