group datasets by meta.Crop #466
Assignees
Comments
Changes ImplementedUpdated the library which will be used for this work : |
Don-Isdale
added a commit
that referenced
this issue
Jan 2, 2025
part of #465 : #466, #467. manage-explorer.js : dataPre1() : insert filter by .cropFilterSelected. dataPre() : rename to dataPostNameFilter, and use alias to define it, so that filters can be inserted easily (dataPre is used in several places); e.g. dataPostCrop() was drafted to implement the crop filter, which is now implemented in dataPre1(), upstream of the name filter, whereas dataPre is downstream of the name filter, as indicated by the name dataPostNameFilter. add noCrop, cropFilterSelected, selectedCropChanged, cropField, withCrop, child1Crop, cropNames (these are based on respectively noGroup, groupFilterSelected, selectedGroupChanged, withParent, child1, parents, parentNames, substituting parent → crop). add cropsForFilter. dataset.js : add cropName : alias(_meta.Crop). filter-group.js : toString() : reduce trace. manage-explorer.hbs : Use form/select-group, with .cropFilterSelected, .cropsForFilter, .selectedCropChanged
Implementation updateBecause only filtering and not grouping is required, it was sufficient, and simpler, to implement the Crop Names list using computed properties based on withParent / parentNames. The list is displayed for user selection, using select-group which is used for the Group selector. These changes are recorded in this comment. Tested on localScreenshots demonstrated the implemented functionality are recorded in #467 in this comment. |
Don-Isdale
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
part of #465
group datasets by meta.Crop (initially considered meta.cropName)
The text was updated successfully, but these errors were encountered: