GitLab

and Method data, however, new code is essentially untested: you've been
warned!!!

models, propagating changes through all three levels and adding suitable
methods to the TraitService to suit.

I now also test for the existence of Property ('Parameter') and Method
objects based on sensible match criteria. When such meta-data records
already exist, I simply return them back to the caller (without
attempting to create a duplicate, which triggers a database constraint
error... but such existing records are logged).

API

category and property ("trait" or Parameter) otherwise seems to work.
The next part for validation if Method.

croprules are null (from the database retrieval) before attempting for
iteration to serialize.

infinite recursion?

* added "getCategory" calling ParameterCategoryRepository "findByName"
method. Used in TraitsController "createCategory" method to retrieve
existing categories

* added "getParameter" calling ParameterRepository "findByCropAndTitle"
method. Used in TraitsController "createParameter" method to retrieve
existing parameters

modified the /methods call to /{propertyId}/method.

the REST API)

more cropService htmlsanitization?

Partially remove htmlsanitation as not required

method, ParameterCategory findParameterCategoryByName(String name); in
the ParameterCategoryRepository interface, and a REST API call to access
the subsystem, in TraitsController.

#10515

#10511