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

Bind this.handleApiError in PodDetail #84

Merged
merged 2 commits into from
Dec 22, 2017
Merged

Bind this.handleApiError in PodDetail #84

merged 2 commits into from
Dec 22, 2017

Conversation

rmars
Copy link

@rmars rmars commented Dec 21, 2017

In #65 I forgot to bind handleApiError in the PodDetail module, which resulted in this error if a fetch call failed:

Uncaught (in promise) TypeError: Cannot read property 'setState' of undefined

This adds that binding.

@rmars rmars added the area/web label Dec 21, 2017
@rmars rmars self-assigned this Dec 21, 2017
Copy link
Contributor

@klingerf klingerf left a comment

Choose a reason for hiding this comment

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

⭐️ Looks good to me.

Copy link
Contributor

@franziskagoltz franziskagoltz left a comment

Choose a reason for hiding this comment

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

lgtm 🎉

@@ -17,9 +17,9 @@ export default class Deployments extends React.Component {
constructor(props) {
super(props);
this.api = ApiHelpers(this.props.pathPrefix);
this.handleApiError = this.handleApiError.bind(this);
Copy link
Contributor

Choose a reason for hiding this comment

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

nice alphabetizing 🔤

@rmars rmars merged commit 4389a1e into master Dec 22, 2017
@rmars rmars deleted the rmars/fix-errors branch December 22, 2017 21:54
pcalcado pushed a commit that referenced this pull request Dec 27, 2017
pcalcado pushed a commit that referenced this pull request Dec 27, 2017
khappucino pushed a commit to Nordstrom/linkerd2 that referenced this pull request Mar 5, 2019
The `metrics!` macro is currently local to the telemetry module.
Furthermore, the `telemetry::metrics` module no longer has
proxy-specific logic.

This change moves the `telemetry::metrics` module into a new crate,
`linkerd2_metrics`.

This will enable unifying `telemetry::http` and `telemetry::transport`
into `http` and `transport`, respectively.
khappucino pushed a commit to Nordstrom/linkerd2 that referenced this pull request Mar 5, 2019
Following linkerd#84, the `telemetry::transport` module can be moved into the
`transport` module.

This should allow us to simplify type signatures by combining redundant
types. It's also hoped that we can reduce the API boilerplate around
metrics so it's much easier to instrument and track new metrics in
transport code.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants