Skip to content
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

Updated funnel schemas #4

Merged
merged 3 commits into from Jul 7, 2017
Merged

Conversation

michael-erasmus
Copy link
Contributor

Hi @davidgasquez! As we discussed, here is the PR with the new funnel and funnel events protobuf and gRPC service schema's

Brief summary of the changes:

  • Seperated funnels and funnel events
  • Added a TrackFunnel rpc
  • Broke out custom uuid message for id's
  • Brought funnel and funnel event schemas in line with current schema
  • Moved funnel tags to be a map and remove the FunnelTag message
  • Created a Link schema for generic data linking

- Seperated funnels and funnel events
- Added a TrackFunnel rpc
- Broke out custom uuid message for id's
- Brought funnel and funnel event schemas in line with current schema
- Moved funnel tags to be a map and remove the FunnelTag message
- Created a Link schema for generic data linking

package buda.entities;

message UUID {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like this approach! 😄 I did a bit of 🔍 and seems there's an open issue to represent UUIDs in protobufs.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Kinda a more general question but, how do you think we could name messages like UTMs or UUIDs. For UTMs I used their style guide recommendationsbut I wasn't 100% sure if that was a good fit.

Looking at their go Uuid, seems it's CamelCase but happy to use any style and stick with it!

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking at their go Uuid, seems it's CamelCase but happy to use any style and stick with it!

Good one @davidgasquez! To be honest, I glossed over the naming a bit and didn't give it much thought.

Happy to use Uuid instead!

Copy link
Contributor

@davidgasquez davidgasquez left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR @michael-erasmus! I left a couple of comments in the code but looks good to me. 😄

As I said in our sync, feel free to change anything in the repo, including the folder structure if this one doesn't make sense or you think it could be simplified!


package buda.entities;

message UUID {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Kinda a more general question but, how do you think we could name messages like UTMs or UUIDs. For UTMs I used their style guide recommendationsbut I wasn't 100% sure if that was a good fit.

Looking at their go Uuid, seems it's CamelCase but happy to use any style and stick with it!


import "buda/entities/uuid.proto";

message Link {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Curious if you see Link being used in other entities? Thinking it could be moved inside funnel_event.proto if not! 😊

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@davidgasquez Yeah, was kind of on the fence on that, but I thought 'maybe' it could be used by other entities. Reflecting on it now, I'm thinking perhaps I should stick to the current use case!

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@davidgasquez still can't make up my mind on this one :D Maybe I could keep things as is (still want to validate if the whole Links idea is worth it) and come back to it later (before we go 'live')

@michael-erasmus michael-erasmus merged commit 7a3daed into master Jul 7, 2017
@davidgasquez davidgasquez deleted the task/update-funnel-schemas branch July 10, 2017 10:11
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.

None yet

2 participants