{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":228104791,"defaultBranch":"master","name":"go-cty-debug","ownerLogin":"zclconf","currentUserCanPush":false,"isFork":false,"isEmpty":false,"createdAt":"2019-12-14T23:46:11.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/28957467?v=4","public":true,"private":false,"isOrgOwned":true},"refInfo":{"name":"","listCacheKey":"v0:1576367194.0","currentOid":""},"activityList":{"items":[{"before":"8c45e122ae1adb59beeb324da553f67a6ee80a08","after":"0d6042c539401a57fc0cca85ded2861d4a5173c4","ref":"refs/heads/master","pushedAt":"2024-05-09T01:02:17.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"apparentlymart","name":"Martin Atkins","path":"/apparentlymart","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20180?s=80&v=4"},"commit":{"message":"cmp: Don't panic if a marked value needs transforming\n\nFor the subset of types that we transform into simpler cmpable types, we\nneed to unmark the value before trying to disassemble it for comparison.\n\nHowever, we don't want to erase the marks entirely since that would make\nit impossible to test whether marking is happening correctly, so instead\nwe wrap any transformation of a marked value in a new struct type\nctyMarkedVal, which then allows the marks to remain associated with the\nvalue even though it isn't a cty.Value anymore.","shortMessageHtmlLink":"cmp: Don't panic if a marked value needs transforming"}},{"before":"b8d9e32151be0b49e010078155c4e6a456ff0590","after":"8c45e122ae1adb59beeb324da553f67a6ee80a08","ref":"refs/heads/master","pushedAt":"2024-04-17T16:04:14.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"apparentlymart","name":"Martin Atkins","path":"/apparentlymart","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20180?s=80&v=4"},"commit":{"message":"CmpOptions: now includes a comparer for cty.Path\n\nThis is in addition to the existing handling of cty.Type and cty.Value,\nso that a caller working with cty concepts can rely just on this single\nset of cmp options for all three of these cty-specific types.","shortMessageHtmlLink":"CmpOptions: now includes a comparer for cty.Path"}},{"before":"b22d67c1ba0bcee1000318b54887fcd6180fbb58","after":"b8d9e32151be0b49e010078155c4e6a456ff0590","ref":"refs/heads/master","pushedAt":"2024-02-09T21:30:25.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"apparentlymart","name":"Martin Atkins","path":"/apparentlymart","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20180?s=80&v=4"},"commit":{"message":"cmp: Avoid tripping cmp's cyclic transformer check\n\nAfter I initially implemented this, upstream go-cmp introduced a (pretty\nreasonable) recursion limit on transformers to detect when they are just\nfeeding their own results back into themselves.\n\nUnfortunately, this package's cmp transformer now often ends up being\nflagged false-positive for that check because we legitimately do have\nnested transformations to make.\n\nTo mitigate that problem, we'll now do all of the recursion internally\ninside the functions in this package, so that go-cmp believes it's\nperforming only a single layer of transformation and doesn't find itself\nhaving to call the same transformer again to deal with nested values.","shortMessageHtmlLink":"cmp: Avoid tripping cmp's cyclic transformer check"}}],"hasNextPage":false,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAERSj0CAA","startCursor":null,"endCursor":null}},"title":"Activity · zclconf/go-cty-debug"}