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

Update tslint to version 4.1.1 🚀 #246

Closed
wants to merge 1 commit into from

Conversation

greenkeeperio-bot
Copy link
Contributor

Hello lovely humans,

tslint just published its new version 4.1.1.

State Update 🚀
Dependency tslint
New version 4.1.1
Type devDependency

This version is not covered by your current version range.

Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.

I recommend you look into these changes and try to get onto the latest version of tslint.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.

Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?

There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.

Good luck with your project ✨

You rock!

🌴


This pull request was created by greenkeeper.io.

Tired of seeing this sponsor message? ⚡ greenkeeper upgrade

@helfer helfer closed this Jan 7, 2017
@helfer helfer deleted the greenkeeper-tslint-4.1.1 branch January 23, 2017 19:50
trevor-scheer pushed a commit that referenced this pull request May 6, 2020
Remove `willUpdateManifest` method from #251 / #246, for now.
trevor-scheer pushed a commit that referenced this pull request May 6, 2020
op-reg: Follow-up changes to #246.
trevor-scheer pushed a commit that referenced this pull request May 6, 2020
Re-land: Add lifecycle hooks: willUpdateManifest, onUnregisteredOperation, onForbiddenOperation [AP-585] [AP-522]
trevor-scheer pushed a commit that referenced this pull request May 6, 2020
This resolves a number of runtime errors which surfaced in the test suite
for this repository, appearing as:

  TypeError: Cannot read property 'method' of undefined

This was overlooked or not addressed within #158 / #246.

While not ideal, today, Apollo Server has a very real expectation of an HTTP
request context.  That will change in the future.  While we can sometimes
make by without it, that is no longer the case when Engine Reporting is
enabled since it relies on the HTTP "method" property of the HTTP context
when building the traces.  Therefore, we'll need to make sure that we
provide a fake HTTP context to `executeOperation` when testing with Engine
enabled, to ensure that it doesn't fail.

cc @jsegaran
trevor-scheer pushed a commit that referenced this pull request May 12, 2020
Remove `willUpdateManifest` method from #251 / #246, for now.
trevor-scheer pushed a commit that referenced this pull request May 12, 2020
op-reg: Follow-up changes to #246.
trevor-scheer pushed a commit that referenced this pull request May 12, 2020
Re-land: Add lifecycle hooks: willUpdateManifest, onUnregisteredOperation, onForbiddenOperation [AP-585] [AP-522]
trevor-scheer pushed a commit that referenced this pull request May 12, 2020
This resolves a number of runtime errors which surfaced in the test suite
for this repository, appearing as:

  TypeError: Cannot read property 'method' of undefined

This was overlooked or not addressed within #158 / #246.

While not ideal, today, Apollo Server has a very real expectation of an HTTP
request context.  That will change in the future.  While we can sometimes
make by without it, that is no longer the case when Engine Reporting is
enabled since it relies on the HTTP "method" property of the HTTP context
when building the traces.  Therefore, we'll need to make sure that we
provide a fake HTTP context to `executeOperation` when testing with Engine
enabled, to ensure that it doesn't fail.

cc @jsegaran
trevor-scheer pushed a commit that referenced this pull request May 14, 2020
Remove `willUpdateManifest` method from #251 / #246, for now.
trevor-scheer pushed a commit that referenced this pull request May 14, 2020
op-reg: Follow-up changes to #246.
trevor-scheer pushed a commit that referenced this pull request May 14, 2020
Re-land: Add lifecycle hooks: willUpdateManifest, onUnregisteredOperation, onForbiddenOperation [AP-585] [AP-522]
trevor-scheer pushed a commit that referenced this pull request May 14, 2020
This resolves a number of runtime errors which surfaced in the test suite
for this repository, appearing as:

  TypeError: Cannot read property 'method' of undefined

This was overlooked or not addressed within #158 / #246.

While not ideal, today, Apollo Server has a very real expectation of an HTTP
request context.  That will change in the future.  While we can sometimes
make by without it, that is no longer the case when Engine Reporting is
enabled since it relies on the HTTP "method" property of the HTTP context
when building the traces.  Therefore, we'll need to make sure that we
provide a fake HTTP context to `executeOperation` when testing with Engine
enabled, to ensure that it doesn't fail.

cc @jsegaran
trevor-scheer pushed a commit that referenced this pull request May 14, 2020
Remove `willUpdateManifest` method from #251 / #246, for now.
trevor-scheer pushed a commit that referenced this pull request May 14, 2020
This resolves a number of runtime errors which surfaced in the test suite
for this repository, appearing as:

  TypeError: Cannot read property 'method' of undefined

This was overlooked or not addressed within #158 / #246.

While not ideal, today, Apollo Server has a very real expectation of an HTTP
request context.  That will change in the future.  While we can sometimes
make by without it, that is no longer the case when Engine Reporting is
enabled since it relies on the HTTP "method" property of the HTTP context
when building the traces.  Therefore, we'll need to make sure that we
provide a fake HTTP context to `executeOperation` when testing with Engine
enabled, to ensure that it doesn't fail.

cc @jsegaran
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants