Skip to content

Issue #24 ChannelSpec #37

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
May 29, 2019
Merged

Issue #24 ChannelSpec #37

merged 6 commits into from
May 29, 2019

Conversation

elpiel
Copy link
Member

@elpiel elpiel commented May 28, 2019

Implements the Fields for #24 , although it still needs some struct fixtures to be used for the fields (check list bellow) it's pretty much done for the ChannelSpec specific fields:

But they can be handled separate

elpiel added 6 commits May 28, 2019 13:26
- AdUnit
- EventSubmission
- TargetingTag
- domain - ValidatorDesc - rename `id` to `addr`
- domain - ChannelSpec - add all the optional fields & optional DateTime for `active_from`
- domain - channel - fixtures - update `get_channel_spec` fixture with **dummy** data for now
- Cargo.toml - add `rand` to `dev-dependencies`
@elpiel elpiel added this to the 0.2.0 milestone May 28, 2019
@elpiel elpiel mentioned this pull request May 28, 2019
16 tasks
@elpiel elpiel merged commit eeb35f8 into master May 29, 2019
elpiel added a commit that referenced this pull request May 29, 2019
@elpiel elpiel deleted the issue-24-channel-spec branch May 29, 2019 05:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant