Jira (PUP-11663) max/min core functions are incorrect for Semver types

[Sean Millichamp (Jira)]

Title: Message Title

Sean Millichamp created an issue   Puppet / PUP-11663 max/min core functions are incorrect for Semver types Issue Type: Improvement Affects Versions: PUP 7.20.0 Assignee: Henrik Lindberg Components: Functions Created: 2022/10/25 11:39 AM Priority: Normal Reporter: Sean Millichamp The Puppet max/min functions do not handle Semver types correctly. The "Any" data type function signature matches, they are converted to strings, compare as strings, and are often incorrect. Based on the spec tests for max/min it looks to be explicitly called out behavior, which I assume it means that it can't change until a new major Puppet version: https://github.com/puppetlabs/puppet/blob/main/spec/unit/functions/max_spec.rb#L77 It would be great if min/max would support all the applicable data types in their native/correct fashion. At least Semver, Timestamp, and Timespan should all be added and the deprecated Any behavior removed. Add Comment   This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.473277.1666723189000.52190.1666723200202%40Atlassian.JIRA.