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

Merge Chrome and Firefox implementations #19

Merged
merged 5 commits into from
Sep 4, 2017
Merged

Merge Chrome and Firefox implementations #19

merged 5 commits into from
Sep 4, 2017

Conversation

SimenB
Copy link
Contributor

@SimenB SimenB commented Sep 2, 2017

I uploaded the resulting zipfile for Chrome to Mozilla's online check for compat (https://www.extensiontest.com/).

image

So this PR ports all of the build from gulp to webpack, and deletes all of the firefox code.

I still want to add add https://github.com/mozilla/webextension-polyfill which allows us to not use any chrome APIs directly. We can also simplify much of the code which is written to abstract over the browser differences. The polyfill also gives us Promise APIs, which another chunk of the code in this repo also does. Done

@@ -1,12 +1,12 @@
{
"name": "zipkin-browser-extension",
"version": "0.0.0",
"version": "0.0.4",
Copy link
Contributor Author

@SimenB SimenB Sep 2, 2017

Choose a reason for hiding this comment

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

In the future bump this to change version instead of VERSION file.

npm version is great for it (creates a git commit as well as a tag)

@SimenB SimenB changed the title Remove firefox specific code Merge Chrome and Firefox implementations Sep 2, 2017
@SimenB
Copy link
Contributor Author

SimenB commented Sep 2, 2017

@adriancole @eirslett This can be reviewed & (hopefully) merged. I'd like to add some tests before release, but I'm also gonna do a small reorganizing of the files, and then git thinks it's all new files. So (squash) merging this separately makes for a more accurate history 🙂

"persistent": true
},
"icons": {
"48": "icon64.png"
Copy link
Contributor Author

@SimenB SimenB Sep 2, 2017

Choose a reason for hiding this comment

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

This shows an icon, so sorta #2. Would like that SVG though

@codefromthecrypt
Copy link
Member

codefromthecrypt commented Sep 4, 2017

fyi "npm run dev-chrome" or firefox doesn't work (might be unrelated)

@SimenB
Copy link
Contributor Author

SimenB commented Sep 4, 2017

It's just npm run dev now, no difference between chrome and firefox 🙂

@codefromthecrypt
Copy link
Member

was able to test chrome via your instructions

However, FF doesn't seem to like the build directory (when I go to install add-on from file)

@codefromthecrypt codefromthecrypt merged commit aad5261 into openzipkin:master Sep 4, 2017
@codefromthecrypt
Copy link
Member

decided on gitter to handle FF separately

@SimenB SimenB deleted the remove-gulp branch September 4, 2017 13:53
@@ -2,7 +2,8 @@ export default function addNetworkEvents(network, pubsub) {
network.onNavigated.addListener(() => {
pubsub.pub('navigated');
});
network.onRequestFinished.addListener(request => {
// https://bugzilla.mozilla.org/show_bug.cgi?id=1311171
network.onRequestFinished && network.onRequestFinished.addListener(request => {
Copy link
Contributor Author

Choose a reason for hiding this comment

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

For posterity, this is why FF doesn't work yet

@SimenB SimenB mentioned this pull request Sep 4, 2017
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.

2 participants