René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Adjust color type to make it more safe","articleBody":"## The problem\r\n\r\nNow that we have `PlatformColor` (nice implementation btw), I think we should think about color not being a type alias to string anymore [(part reversal of this PR)](https://github.com/rescript-react-native/rescript-react-native/pull/448). I would like to gradually start to use platform colors in my app, now all colors are strings, and sometimes I do some manipulation on them (like darken/lighten), of course that wouldn't work on platform colors.\r\n\r\n## Considered solution\r\n\r\nSo to make colors safe I think we should make them phantom typed.\r\n\r\n```\r\ntype t\u003c'a\u003e\r\nexternal string: string =\u003e t\u003cstring\u003e = \"%identity\"\r\nexternal get: color\u003c'a\u003e =\u003e 'a = \"%identity\"\r\n...\r\nlet blue = Color.string(\"blue\")\r\n\r\nlet blueString = Color.get(blue)\r\n```\r\n\r\nWith platform colors being `color\u003cPlatformColor.t\u003e`.\r\n\r\nIn `Style.t` we can accept all colors (we need a lot of type parameters in the external though)\r\n\r\n##  Alternative solution\r\n\r\nAn opaque type. The type of the color would be lost, so we can't easily have a `get` or `toString` that would raise a type error for a platform color. The upside for this is that we need less type parameters.","author":{"url":"https://github.com/jfrolich","@type":"Person","name":"jfrolich"},"datePublished":"2021-06-21T02:57:33.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":8},"url":"https://github.com/746/rescript-react-native/issues/746"}