caribou-code

caribou-code

Member Since 6 years ago

Experience Points
3
follower
Lessons Completed
0
follow
Lessons Completed
4
stars
Best Reply Awards
2
repos

14 contributions in the last year

Pinned
⚡ A DRY and modular grid framework built with SCSS using attribute modules and flexbox
⚡ Simple blockchain experiment
Activity
Nov
18
2 months ago
Activity icon
issue

caribou-code issue postmanlabs/postman-flows

caribou-code
caribou-code

Unable to assign collection variables and persist values through an entire flow

I have a very common flow pattern that looks like this:

  1. Get access token a. Set as collection variable via Test tab on request b. Set bearer token header at the collection level via Authorization tab
  2. Get A from B endpoint (uses collection authorization header)
  3. Get X from Z endpoint (uses collection authorization header)

The test tab for step 1 looks like this:

const { access_token } = JSON.parse(responseBody);
pm.collectionVariables.set('accessToken', access_token);
console.log(access_token);

const accessToken = pm.collectionVariables.get('accessToken');
console.log(accessToken);

The 2 logged values are the same, so on the surface it looks like the collection variable has been set, but when I manually check the collection variables list, I see the variable has not been set. This issue only exists when using Postman flows.

Seems like a fairly common pattern to me for any APIs that require an authorization header on every request, so this bug currently renders Postman Flows unusable for me.

Note: Using the assign variables and create variables blocks in Postman Flows is not a possible solution here because I need the access token to persist across all requests in the flow, so the variable needs to be scoped at a shared level.

Oct
25
2 months ago
Activity icon
issue

caribou-code issue comment facebook/react

caribou-code
caribou-code

Bug: Rules with suggestions must set the `meta.hasSuggestions` property to `true`

I'm basically running into an issue where eslint is asking me to set meta.hasSuggestions to true. When I use "react-hooks/exhaustive-deps": "error". Is there something I'm doing wrong or is this a dep version thing?

React version:

Steps To Reproduce

  1. Have my eslint config:
{
  "env": {
    "browser": true,
    "es2021": true
  },
  "extends": [
    "eslint:recommended",
    "plugin:react/recommended",
    "plugin:react-hooks/recommended",
    "plugin:@typescript-eslint/recommended",
    "prettier"
  ],
  "parser": "@typescript-eslint/parser",
  "parserOptions": {
    "ecmaFeatures": {
      "jsx": true
    },
    "ecmaVersion": 13,
    "sourceType": "module"
  },
  "plugins": ["react", "react-hooks", "@typescript-eslint"],
  "rules": {
    "react-hooks/exhaustive-deps": "error",
  },
  "settings": {
    "react": {
      "version": "detect"
    }
  }
}

Here's my deps from package.json

{
"dependecies": {
    "eslint": "^8.0.0",
    "eslint-config-prettier": "^8.3.0",
    "eslint-plugin-react": "^7.26.1",
    "eslint-plugin-react-hooks": "^4.2.0",
}

If I try to remove the react-hook plugin and extension this happens: Definition for rule 'react-hooks/exhaustive-deps' was not found

Link to code example:

The current behavior

The expected behavior

caribou-code
caribou-code

Is there a release date for this yet? Looks like the fix was merged on 6 Sept.