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

chore(CHANGELOG): update to v0.14.0 #54

Merged
merged 1 commit into from
Nov 3, 2022
Merged

chore(CHANGELOG): update to v0.14.0 #54

merged 1 commit into from
Nov 3, 2022

Conversation

philippfromme
Copy link
Collaborator

@philippfromme philippfromme commented Nov 3, 2022

Changes

  • FEAT: add feel rule to validate feel expressions (#51)
  • FEAT: add collapsed-subprocess rule to disallow collapsed subprocess (#52)
  • CHORE: element-type rule handles all errors using ELEMENT_TYPE_NOT_ALLOWED error type (#50)
  • CHORE: timer rule handles bpmn:FormalExpression elements using new error types EXPRESSION_REQUIRED and EXPRESSION_VALUE_NOT_ALLOWED (#50)
  • CHORE: refactor configuration of rules (#50)

Breaking Changes

  • rules that need configuration (e.g. element-type) are now configured by specifying execution platform version
  • element-type rule only reports ELEMENT_TYPE_NOT_ALLOWED errors
  • timer rule reports new error types EXPRESSION_REQUIRED and EXPRESSION_VALUE_NOT_ALLOWED
  • report.error was renamed to report.data as it is meant to be used for any additional data
  • ERROR_TYPES were namespaced to avoid mistaking reports with report.data.type for Camunda-specific reports

@bpmn-io-tasks bpmn-io-tasks bot added the needs review Review pending label Nov 3, 2022
CHANGELOG.md Outdated
* timer rule reports new error types `EXPRESSION_REQUIRED` and `EXPRESSION_VALUE_NOT_ALLOWED`
* `report.error` was renamed to `report.data` as it is meant to be used for any additional data
* `ERROR_TYPES` were namespaced to avoid mistaking reports with `report.data.type` for Camunda-specific reports
* `FEEL_INVALID` error type renamed to `FEEL_EXPRESSION_INVALID`
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
* `FEEL_INVALID` error type renamed to `FEEL_EXPRESSION_INVALID`

FEEL_INVALID was not released yet

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Yeah, it's going to be released as part of v0.14.0: 4005780

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Sorry, now I get what you mean.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

So, no breaking change as this didn't exist previously. 👍🏻

Copy link
Member

Choose a reason for hiding this comment

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

Exactly 💯

Copy link
Member

@marstamm marstamm left a comment

Choose a reason for hiding this comment

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

🚀

@merge-me merge-me bot merged commit 7e83f51 into main Nov 3, 2022
@merge-me merge-me bot deleted the changelog branch November 3, 2022 14:08
@bpmn-io-tasks bpmn-io-tasks bot removed the needs review Review pending label Nov 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants