7am PST / 4pm CET
Toll: +1-415-655-0001
Number: 199 948 686
Time | Item | Who | Notes |
---|---|---|---|
5m | Action Item review from last time | Josh Zamor | |
30m | Demo data loading | Chongsun Ahn (Unlicensed) | Problem statement and options for solution |
Review dev forum post(s) on error messages | Paweł Albecki (Deactivated) and Brandon Bowersox-Johnson | Dev forum post: https://groups.google.com/forum/#!topic/openlmis-dev/iwGo2mLR3wk | |
5m | Multi-cloud / evaluating Azure | Ben Leibert | Note: may not be ready for this yet |
Non-functional requirement progress - performance? | Sort of did this in showcase | ||
IDs in DTO's equals and hashcode - effects on etags | Chongsun Ahn (Unlicensed) | Note: May not be ready for this quite yet |
New approaches:
UUID's generated:
Dev forum had already focused on option 3 - use the top level error message with some section below that. Keeps backward compatability.
Further we discussed the idea for nesting (details within details) which seems like something we could do if needed. Ideas for usage was something along the lines of semantically structuring error messages (e.g. there's an error, there's an error in the budget, there's an error in budget line item 5) or directly down to a line item.
Between fieldErrors or renaming it to details we felt there's value in just keeping it a direct "fieldErrors" name.
Intuitive and modern UI – great for organizations which are less technical but nevertheless interested in maintaining their own OpenLMIS instance.