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.

Sign up for GitHub

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

Jump to bottom

🗑️ Deprecation promotion of toStrictlyPositiveInt function in ResultContext to error level #447

Closed
1 of 3 tasks
Tracked by #448
, #587
...
LVMVRQUXL opened this issue Feb 8, 2024 · 1 comment
Closed
1 of 3 tasks
Tracked by #448
, #587
...

🗑️ Deprecation promotion of toStrictlyPositiveInt function in ResultContext to error level #447

LVMVRQUXL opened this issue Feb 8, 2024 · 1 comment
Labels
common Item related to all platforms. feature New feature or request.

Comments

@LVMVRQUXL
Copy link
Contributor

LVMVRQUXL commented Feb 8, 2024 •
edited
Loading

📝 Description

We would like to promote the deprecation of the toStrictlyPositiveInt function in ResultContext to an error level.

🔗 Dependencies

This issue is blocked by the following ones:

✅ Checklist

  • Promote the deprecation of this declaration, remove its tests and update the unreleased changelog.
  • Close this issue as completed and update tracking ones if present.
@LVMVRQUXL LVMVRQUXL added feature New feature or request. common Item related to all platforms. labels Feb 8, 2024
@LVMVRQUXL LVMVRQUXL added this to the 5.3.0 milestone Feb 8, 2024
@LVMVRQUXL LVMVRQUXL mentioned this issue Feb 8, 2024
Closed
3 tasks
@LVMVRQUXL LVMVRQUXL modified the milestones: 5.3.0, 5.4.0 Feb 21, 2024
@LVMVRQUXL LVMVRQUXL changed the title Deprecation promotion of toStrictlyPositiveInt function in ResultContext to error level 🗑️ Deprecation promotion of toStrictlyPositiveInt function in ResultContext to error level Feb 27, 2024
@LVMVRQUXL LVMVRQUXL mentioned this issue Mar 17, 2024
Closed
@LVMVRQUXL LVMVRQUXL removed this from the 5.4.0 milestone Mar 22, 2024
@LVMVRQUXL
Copy link
Contributor Author

We are not ready to implement this change.

@LVMVRQUXL LVMVRQUXL closed this as not planned Won't fix, can't repro, duplicate, stale Mar 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
common Item related to all platforms. feature New feature or request.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@LVMVRQUXL