v0.20.0 with BREAKING CHANGES - ternary expressions formatting updates coming again

[brodybits]

Considering that the new --offset-ternary-expressions option did not really resolve the inconsistent nested ternary formatting issue in #41 and led to another issue in #468, and that a simpler solution in PR #492 seems to resolve the nested ternary formatting, I am thinking about renaming the option again.

I would like to request that people raise any objections ASAP as I would like to make the new release with the simpler solution in PR #492 in the near future.

@aMarCruz as I said in PR #492 this would likely undo some changes that you contributed in the past.

/cc @aMarCruz @sheerun

---

UPDATE 1 (June 2021): I would like to make some updates to resolve outdated dependencies as discussed in issue #587 before making these breaking changes.

Update 2 (June 2021): Now that the npm audit issues from issue #587 have been resolved, I would like to make this update (in prettierX release 0.19.0) before merging the updates from Prettier 2.3.1.

Please see the following for more information:

• issue [prettierx] more flexible ternary conditional expression formatting #585
• PR [WIP] prettierx refactor!: fix & update balanced ternary formatting support - DRAFT WIP #620

[aMarCruz]

@brodybits no problem with that.

[brodybits]

FYI I am planning (again) to make these breaking changes in upcoming 0.19.0 release, before merging updates from Prettier 2.3.1.

update: These updates are again slated for upcoming prettierX release 0.20.0.

Please see the following for more information:

• issue [prettierx] more flexible ternary conditional expression formatting #585
• PR [WIP] prettierx refactor!: fix & update balanced ternary formatting support - DRAFT WIP #620