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

Update dependency ts-enum-util to v4 #10

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Mar 22, 2019

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
ts-enum-util 3.1.0 -> 4.0.2 age adoption passing confidence

Release Notes

UselessPickles/ts-enum-util

v4.0.2: Removed peer dependency on TypeScript

Compare Source

The peer dependency on TypeScript was more trouble than it was worth. See #​16

v4.0.1: Non-positive-integer enum value bug fixes

Compare Source

This is a bug fix for numeric enums whose values are not all positive integers.

The code that gets all of the keys of an enum (ignoring the reverse lookup keys that typescript automatically adds) incorrectly assumed that all numeric enum values (and therefore the reverse lookup keys) would be limited valid array index values (basically, non-negative integers within the range of a signed 32-bit value).

This was a bad assumption. Numeric enums can contain any numeric values, including floating point and negative values. The end result was widespread bugs if you had a numeric enum values that was negative or not an integer.

v4.0.0: New Value Visitor/Mapper Functionality

Compare Source

Huge New Feature!

The functionality of ts-string-visitor (npm, github) has been merged into ts-enum-util and improved to also support numeric literal/enum values. See the README for a link to full documentation of Value Visitor/Mapper functionality, and also a Migration Guide if you previously used ts-string-visitor.

This unfortunately brought with it a breaking change: TypeScript 2.9 is now the minimum supported version.

Other New Features

  • (possibly breaking) The iteration/sort order of enum entries/values/keys is no longer based on sorted key order. The original defined order of the enum is now retained (guaranteed in ES6 environments due to language spec, all but guaranteed in non-ES6 environments due to de-facto standards of nearly all implementations). This is more likely to give desired results if you use $enum().map() to create options for a dropdown UI component, for example.
  • New $enum().indexOfValue() to get the index of an enum entry based on a value. Can be useful for implementing sort comparators for grids, etc.
  • New $enum().indexOfKey() to get the index of an enum entry based on a key. Can be useful for implementing sort comparators for grids, etc.

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/ts-enum-util-4.x branch from 293f0f1 to 58bef65 Compare April 25, 2019 02:18
@renovate renovate bot force-pushed the renovate/ts-enum-util-4.x branch from 58bef65 to 1609014 Compare June 15, 2019 21:46
@renovate renovate bot force-pushed the renovate/ts-enum-util-4.x branch from 1609014 to 36bfe63 Compare June 6, 2020 02:30
@sonarcloud
Copy link

sonarcloud bot commented Jun 6, 2020

Kudos, SonarCloud Quality Gate passed!

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities (and Security Hotspot 0 Security Hotspots to review)
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@renovate
Copy link
Author

renovate bot commented Mar 24, 2023

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

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.

1 participant