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

fix(intercom): fix date conversion from unix timestamp to js date of intercom attributes #742

Merged
merged 2 commits into from
Jun 15, 2021

Conversation

jeffladiray
Copy link
Member

@jeffladiray jeffladiray commented Jun 14, 2021

Close #640

Pull Request checklist:

  • Write an explicit title for the Pull Request, following Conventional Commits specification
  • Test manually the implemented changes
  • Review my own code (indentation, syntax, style, simplicity, readability)
  • Wonder if you can improve the existing code

@codeclimate
Copy link

codeclimate bot commented Jun 14, 2021

Code Climate has analyzed commit fc1bb91 and detected 1 issue on this pull request.

Here's the issue category breakdown:

Category Count
Complexity 1

The test coverage on the diff in this pull request is 100.0% (60% is the threshold).

This pull request will bring the total coverage in the repository to 55.4%.

View more on Code Climate.

@jeffladiray jeffladiray marked this pull request as ready for review June 14, 2021 13:45
@forest-bot
Copy link
Member

Copy link
Contributor

@GuillaumeCisco GuillaumeCisco left a comment

Choose a reason for hiding this comment

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

Tested! 🏁
Works great! 🎉

@jeffladiray jeffladiray merged commit 97fa090 into master Jun 15, 2021
@jeffladiray jeffladiray deleted the fix/intercom-timestamp-to-js-date branch June 15, 2021 08:45
forest-bot added a commit that referenced this pull request Jun 15, 2021
## [8.7.2](v8.7.1...v8.7.2) (2021-06-15)

### Bug Fixes

* **intercom:** fix date conversion from unix timestamp to js date of intercom attributes ([#742](#742)) ([97fa090](97fa090))
@forest-bot
Copy link
Member

🎉 This PR is included in version 8.7.2 🎉

The release is available on:

Your semantic-release bot 📦🚀

forest-bot added a commit that referenced this pull request Jun 16, 2021
# [9.0.0-beta.7](v9.0.0-beta.6...v9.0.0-beta.7) (2021-06-16)

### Bug Fixes

* stats permissions should be retrieved only one time per team ([#741](#741)) ([8d05d75](8d05d75))
* **intercom:** fix date conversion from unix timestamp to js date of intercom attributes ([#742](#742)) ([97fa090](97fa090))
* prevent IP check from failing for the proxies including the port in the headers ([#738](#738)) ([810d0c1](810d0c1))

### Features

* include role in the user data inside the request ([#733](#733)) ([e74ce72](e74ce72))
@forest-bot
Copy link
Member

🎉 This PR is included in version 9.0.0-beta.7 🎉

The release is available on:

Your semantic-release bot 📦🚀

ShohanRahman pushed a commit that referenced this pull request Jan 25, 2022
… action form (#742)

BREAKING CHANGE: fields parameters on hook function is no longer a map of field, it is now an array.
change hook is no longer choosen by the field name, field need to have hook defined inside it definition by addin a props hook.
ShohanRahman pushed a commit that referenced this pull request Jan 25, 2022
# [8.0.0-beta.7](ForestAdmin/forest-express-sequelize@v8.0.0-beta.6...v8.0.0-beta.7) (2021-06-07)

### Features

* **smart-action:** user can add dynamically field with hook on smart action form ([#742](ForestAdmin/forest-express-sequelize#742)) ([228bb42](ForestAdmin/forest-express-sequelize@228bb42))

### BREAKING CHANGES

* **smart-action:** fields parameters on hook function is no longer a map of field, it is now an array.
change hook is no longer choosen by the field name, field need to have hook defined inside it definition by addin a props hook.
ShohanRahman pushed a commit that referenced this pull request Jan 25, 2022
# [8.0.0](ForestAdmin/forest-express-sequelize@v7.12.2...v8.0.0) (2021-07-19)

### Bug Fixes

* abstractRecord type ([#772](ForestAdmin/forest-express-sequelize#772)) ([81492b9](ForestAdmin/forest-express-sequelize@81492b9))
* correctly get the IP address from the request headers ([2b5ed1d](ForestAdmin/forest-express-sequelize@2b5ed1d))
* fix types ([580ef41](ForestAdmin/forest-express-sequelize@580ef41))

### Features

* allow hooks for global and bulk smart action ([#769](ForestAdmin/forest-express-sequelize#769)) ([14c26cd](ForestAdmin/forest-express-sequelize@14c26cd))
* **browsing-context:** allow `Forest-Context-Url` header to give the current browser url of users ([#665](ForestAdmin/forest-express-sequelize#665)) ([c46fd66](ForestAdmin/forest-express-sequelize@c46fd66))
* **browsing-context:** allow `Forest-Context-Url` header to give the current browser url of users ([#665](ForestAdmin/forest-express-sequelize#665)) ([a61699a](ForestAdmin/forest-express-sequelize@a61699a))
* **security:** secure segments queries ([#764](ForestAdmin/forest-express-sequelize#764)) ([98d7f74](ForestAdmin/forest-express-sequelize@98d7f74))
* **smart-action:** user can add dynamically field with hook on smart action form ([#742](ForestAdmin/forest-express-sequelize#742)) ([228bb42](ForestAdmin/forest-express-sequelize@228bb42))

* feat(scopes)!: enforce scopes restrictions on a wider range of requests (#731) ([da7d71d](ForestAdmin/forest-express-sequelize@da7d71d)), closes [#731](ForestAdmin/forest-express-sequelize#731)

### BREAKING CHANGES

* record is no longer send to the hook middleware & values option on smart action is no longer supported
* **smart-action:** fields parameters on hook function is no longer a map of field, it is now an array.
change hook is no longer choosen by the field name, field need to have hook defined inside it definition by addin a props hook.
* the public API of forest-express has changed to include the parameters which are needed to evaluate scope filters. This includes PermissionMiddlewareCreator, all classes on the /exposed folder and most services. Many routes now require providing the current user timezone.
* **browsing-context:** users willing to use this header needs either to clean the allowed headers or to add this specific header in the CORS configuration
* **browsing-context:** users willing to use this header needs either to clean the allowed headers or to add this specific header in the CORS configuration
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Intercom: dates are all in 1970
3 participants