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

Add taxonomy #408

Merged
merged 234 commits into from
Apr 22, 2016
Merged

Add taxonomy #408

merged 234 commits into from
Apr 22, 2016

Conversation

JohanLorenzo
Copy link
Contributor

No description provided.

David Rajchenbach-Teller and others added 30 commits February 18, 2016 10:37
Issue #6 - Remove generated doc from repository.
For a first version, let's do without subnodes. We can always add them
later if we find out that they are needed.
… to make them future-proof.

In the original version, requests were implemented as a `struct` with
`pub` fields. That's going to cause code breakage if we decide to add
or rework fields in the future (e.g. to restore subnodes). This patch
replaces the public fields with a proper API that may be used to
create and combine requests.
David Rajchenbach-Teller and others added 17 commits April 13, 2016 11:35
Better deserialization error messages
Add WebPushNotify type for webpush adapter
Better deserialization error messages
…of 'typ' - matching the deserialization format.
When serialized, extension now sends 'type' instead of 'typ' - matchi…
Adding ChannelKind::ExecuteEveryInterval, ExecuteAfterDelay
@coveralls
Copy link

Coverage Status

Coverage increased (+0.7%) to 38.948% when pulling c60382a on JohanLorenzo:add-taxonomy into 6bde3e6 on fxbox:master.

@JohanLorenzo
Copy link
Contributor Author

@mcav
Copy link
Contributor

mcav commented Apr 21, 2016

What will happen to Taxonomy's WIP branches (e.g. fxbox/deprecated-taxonomy#104 ) when we merge this?

@Yoric
Copy link

Yoric commented Apr 21, 2016

We'll need to migrate them manually. @JohanLorenzo has promised to help :)

@JohanLorenzo
Copy link
Contributor Author

Yes, we'll have to manually create the new branches/PRs. A couple of ways I see:

  • Generate a diff and apply it to the new repo
  • git filter-branch to move the files to the correct path, pull the commit in the new repo (but not in a branch yet) and cherry-pick the commits in the right branch.

@@ -0,0 +1,2 @@
target/
Copy link

@Yoric Yoric Apr 21, 2016

Choose a reason for hiding this comment

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

I haven't paid attention for other repos, but is this file necessary?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Good catch. That particular file is not necessary as .gitignore at the root of the repo already takes care of target/ and Cargo.lock. I added an extra commit to clean it up

@Yoric
Copy link

Yoric commented Apr 21, 2016

r=me

@coveralls
Copy link

Coverage Status

Coverage increased (+0.8%) to 39.03% when pulling a66b424 on JohanLorenzo:add-taxonomy into 6bde3e6 on fxbox:master.

@JohanLorenzo JohanLorenzo merged commit 4036f9e into fxbox:master Apr 22, 2016
@JohanLorenzo JohanLorenzo deleted the add-taxonomy branch May 19, 2016 08:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.