mdesousa

mdesousa

Member Since 10 years ago

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

30 contributions in the last year

Pinned
⚡ nivo provides a rich set of dataviz components, built on top of the awesome d3 and Reactjs libraries
Activity
Nov
16
2 weeks ago
Activity icon
issue

mdesousa issue comment MichalLytek/typegraphql-prisma

mdesousa
mdesousa

Add a configuration option to emit original names in decorator options

Hi, thanks for this awesome library!

I would like to request this option to emit the original names in the decorator options. This is to avoid errors when code is processed by a bundler like webpack or esbuild.

Please see this for reference: https://github.com/MichalLytek/type-graphql/issues/963#issuecomment-894459659

Thanks!

mdesousa
mdesousa

@MichalLytek just wanted to confirm that this fixed the issue. Thanks again!

Nov
10
3 weeks ago
Activity icon
issue

mdesousa issue comment MichalLytek/typegraphql-prisma

mdesousa
mdesousa

Add a configuration option to emit original names in decorator options

Hi, thanks for this awesome library!

I would like to request this option to emit the original names in the decorator options. This is to avoid errors when code is processed by a bundler like webpack or esbuild.

Please see this for reference: https://github.com/MichalLytek/type-graphql/issues/963#issuecomment-894459659

Thanks!

mdesousa
mdesousa
Nov
2
1 month ago
Activity icon
fork

mdesousa forked zapier/zapier-platform-example-app-typescript

fork time in 1 month ago
Oct
7
1 month ago
Activity icon
issue

mdesousa issue comment aws-amplify/amplify-js

mdesousa
mdesousa

Refresh token not usable for OAuth authentication when Cognito is enabled to remember devices

Before opening, please confirm:

JavaScript Framework

React

Amplify APIs

Authentication

Amplify Categories

auth

Environment information

# Put output below this line


Describe the bug

We use amazon-cognito-identity-js to authenticate users and obtain refresh / access tokens to call our APIs. We recently enabled Cognito to remember devices with the "Opt-In" option. Before enabling devices, our developers were able to take the refresh token from amazon-cognito-identity-js to obtain an access token (using the oauth token endpoing) that could be used to call our APIs for integration purposes. However, after enabling devices this is not longer working... using the refresh token with the token endpoint results in an "invalid_grant" error.

Expected behavior

Refresh tokens should continue to work for OAuth token endpoint

Reproduction steps

npm install amazon-cognito-identity-js authenticate user with amazon-cognito-idetity-js with a cognito user pool enabled to remember devices const refreshToken = session.getRefreshToken().getToken() Use the refreshToken above to exchange refresh token for tokens, as shown in this example

Code Snippet

// Put your code below this line.

Log output

The request returns invalid_grant

aws-exports.js

No response

Manual configuration

No response

Additional configuration

No response

Mobile Device

No response

Mobile Operating System

No response

Mobile Browser

No response

Mobile Browser Version

No response

Additional information and screenshots

No response

mdesousa
mdesousa

Thanks @chrisbonifacio, we have implemented onSuccess to remember the device as mentioned. However, I'm not sure that this is related to the problem that we are having since the refresh token is the same for either case.

Oct
3
2 months ago
Activity icon
issue

mdesousa issue aws-amplify/amplify-js

mdesousa
mdesousa

Refresh token not usable for OAuth authentication when Cognito is enabled to remember devices

Before opening, please confirm:

JavaScript Framework

React

Amplify APIs

Authentication

Amplify Categories

auth

Environment information

# Put output below this line


Describe the bug

We use amazon-cognito-identity-js to authenticate users and obtain refresh / access tokens to call our APIs. We recently enabled Cognito to remember devices with the "Opt-In" option. Before enabling devices, our developers were able to take the refresh token from amazon-cognito-identity-js to obtain an access token (using the oauth token endpoing) that could be used to call our APIs for integration purposes. However, after enabling devices this is not longer working... using the refresh token with the token endpoint results in an "invalid_grant" error.

Expected behavior

Refresh tokens should continue to work for OAuth token endpoint

Reproduction steps

npm install amazon-cognito-identity-js authenticate user with amazon-cognito-idetity-js with a cognito user pool enabled to remember devices const refreshToken = session.getRefreshToken().getToken() Use the refreshToken above to exchange refresh token for tokens, as shown in this example

Code Snippet

// Put your code below this line.

Log output

The request returns invalid_grant

aws-exports.js

No response

Manual configuration

No response

Additional configuration

No response

Mobile Device

No response

Mobile Operating System

No response

Mobile Browser

No response

Mobile Browser Version

No response

Additional information and screenshots

No response

Sep
14
2 months ago
Activity icon
issue

mdesousa issue comment vazco/uniforms

mdesousa
mdesousa

Required property inside required property does not show error

Let us know what is happening. Do provide us with:

Hi, we are seeing this issue with the following packages: [email protected] [email protected] [email protected]

We have a json schema defined as shown at the bottom... for example: { myObject: { myString: 'x'} } In this scenario, both myObject and myString are required properties. We have a form with an <ErrorField name="myObject.myString" /> The problem occurs when the model is undefined... in that case, ` does not show an error even though the validation fails. We would expect that the error field would show an error in this scenario. Thanks.

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "$ref": "#/definitions/MyType1",
  "definitions": {
    "MyType1": {
      "type": "object",
      "additionalProperties": false,
      "properties": {
        "myObject": {
          "$ref": "#/definitions/MyType2"
        },
      },
      "required": [
        "myObject"
      ]
    },
    "MyType2": {
      "type": "object",
      "properties": {
        "myString": {
          "type": "string"
        }
      },
      "required": [
        "myString"
      ],
      "additionalProperties": false
    },
  }
}
mdesousa
mdesousa

Ah, sorry... it's a simplified version of what we are doing. I'll try to find a way to reproduce it... may take me a few days. Thanks!

Sep
13
2 months ago
Activity icon
issue

mdesousa issue vazco/uniforms

mdesousa
mdesousa

Required property inside required property does not show error

Let us know what is happening. Do provide us with:

Hi, we are seeing this issue with the following packages: [email protected] [email protected] [email protected]

We have a json schema defined as shown at the bottom... for example: { myObject: { myString: 'x'} } In this scenario, both myObject and myString are required properties. We have a form with an <ErrorField name="myObject.myString" /> The problem occurs when the model is undefined... in that case, ` does not show an error even though the validation fails. We would expect that the error field would show an error in this scenario. Thanks.

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "$ref": "#/definitions/MyType1",
  "definitions": {
    "MyType1": {
      "type": "object",
      "additionalProperties": false,
      "properties": {
        "myObject": {
          "$ref": "#/definitions/MyType2"
        },
      },
      "required": [
        "myObject"
      ]
    },
    "MyType2": {
      "type": "object",
      "properties": {
        "myString": {
          "type": "string"
        }
      },
      "required": [
        "myString"
      ],
      "additionalProperties": false
    },
  }
}
Sep
11
2 months ago
Activity icon
issue

mdesousa issue vega/ts-json-schema-generator

mdesousa
mdesousa

Required<T> types do not generate re

Define two types as follows:

export type MyType = {
  prop1?: string
  prop2?: string
}

export type MyRequiredType = Required<MyType>

Expected to see the json schema generated to show prop1 and prop2 listed as required for MyRequiredType However, they are not:

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "definitions": {
    "MyType": {
      "type": "object",
      "properties": {
        "prop1": {
          "type": "string"
        },
        "prop2": {
          "type": "string"
        }
      },
      "additionalProperties": false
    },
    "MyRequiredType": {
      "type": "object",
      "properties": {
        "prop1": {
          "type": "string"
        },
        "prop2": {
          "type": "string"
        }
      },
      "additionalProperties": false
    }
  }
}