Skip to content

Conversation

@brizental
Copy link
Contributor

This is more or less related to Bug 1686678. I did a bit of reserach on that bug to figure out the best way to organize the Glean.js package. In this research I saw other packages that organize their code like I do in this PR and I liked the approach.

I think this way the platform specific and non platform specific code is more clearly separated. As a bonus it is clearer to separate tests that run on the browser and tests that don't.

I also moved all the code into a glean/ folder. That is necessary in order to be able to use npm link to link and use the future @mozilla/glean package in our samples. Turns out we can't use that command if the sample is inside the package folder. To bypass that I move the package into a dedicated folder.

Copy link
Contributor

@Dexterp37 Dexterp37 left a comment

Choose a reason for hiding this comment

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

r+wc

@brizental brizental merged commit a340092 into mozilla:main Feb 16, 2021
@brizental brizental deleted the 1686678-reorg branch February 16, 2021 18:07
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