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

Basic source map support #27

Merged
merged 7 commits into from
Feb 27, 2018
Merged

Basic source map support #27

merged 7 commits into from
Feb 27, 2018

Conversation

jeromegn
Copy link
Member

  • Adds source maps in all environments
  • Deploying also uploads the source map
  • Adds basic unit tests for v8env using our own fly test

Copy link
Contributor

@mbyczkowski mbyczkowski left a comment

Choose a reason for hiding this comment

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

LGTM. I was just curious about some areas and left comments, but not blocking 🙂

@@ -43,10 +44,15 @@ export class App {
return this.releaseInfo.source_hash
}

get sourceMap() {
return this.releaseInfo.source_map
Copy link
Contributor

Choose a reason for hiding this comment

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

Is there a convention for snake case vs camel case (I'm genuinely curious)? do we only use snake case for JSON going to web app?

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes, Ruby's convention is snake_case and since that's what the API is written in, that's the data we receive and need to send.

At some point we should figure out a way to homogenize this. I've never knew what to do in these cases, so I'm just following each language's conventions.

@@ -5,7 +5,7 @@
"main": "lib/index.js",
"scripts": {
"start": "./bin/fly server ./apps/getting-started",
"test": "mocha",
"test": "node ./lib/cmd/index.js test v8env_test/**/*.spec.js && mocha",
Copy link
Contributor

Choose a reason for hiding this comment

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

smartz (using fly test)!

})

setImmediate(() =>
Copy link
Contributor

Choose a reason for hiding this comment

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

not sure what the implication is of changing setImmediate only once request is finalized?

Copy link
Member Author

Choose a reason for hiding this comment

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

It's a readability change. We used to attach the event handlers in the setImmediate also. It just wasn't necessary and made it harder to reason about.

We need that setImmediate only for when we start reading or writing to the body.

@coveralls
Copy link

Pull Request Test Coverage Report for Build 243

  • 32 of 39 (82.05%) changed or added relevant lines in 8 files are covered.
  • 1 unchanged line in 1 file lost coverage.
  • Overall coverage increased (+0.2%) to 73.28%

Changes Missing Coverage Covered Lines Changed/Added Lines %
src/v8env.ts 3 4 75.0%
src/utils/build.ts 0 1 0.0%
src/app/stores/file.ts 0 2 0.0%
src/bridge/fetch.ts 10 13 76.92%
Files with Coverage Reduction New Missed Lines %
src/bridge/fetch.ts 1 89.19%
Totals Coverage Status
Change from base Build 241: 0.2%
Covered Lines: 1069
Relevant Lines: 1373

💛 - Coveralls

@jeromegn jeromegn merged commit 1f7301a into master Feb 27, 2018
@michaeldwan michaeldwan deleted the source-map branch August 15, 2018 16:42
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.

3 participants