Merge lp:~chrismurf-bluefin/dccl/variable-time-codec into lp:~dccl-dev/dccl/3.0
Proposed by
Chris Murphy
Status: | Merged |
---|---|
Merged at revision: | 274 |
Proposed branch: | lp:~chrismurf-bluefin/dccl/variable-time-codec |
Merge into: | lp:~dccl-dev/dccl/3.0 |
Diff against target: |
94 lines (+27/-8) 4 files modified
src/field_codec_default.h (+12/-7) src/protobuf/option_extensions.proto (+3/-0) src/test/dccl_header/header.proto (+6/-1) src/test/dccl_header/test.cpp (+6/-0) |
To merge this branch: | bzr merge lp:~chrismurf-bluefin/dccl/variable-time-codec |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
toby schneider | Approve | ||
Patrick LaRocque | Pending | ||
Review via email: mp+181098@code.launchpad.net |
Description of the change
Adding a parameter to allow TimeCodec to encode times outside the +-12 hour window (24 hours centered around receive time) that it supports now. The parameter is currently named num_days - feel free to rename or request a rename. Small test case added.
I also uncovered something that I wasn't aware of - it seems like TimeCodec can't encode partial seconds? Not a problem for me now, but a surprise. See Bug 1214478.
To post a comment you must log in.
Clean implementation of a sensible feature. I think `num_days` is a fine name for the option extension. The only "better" way we could do it is to add units to DCCL and allow the field and max/min to have different units (e.g. seconds for the field, days for the max/min) and have the conversion done automatically.
But that's a wishlist item, so you have my approval to merge your changes without modification.