Change Details

This is going to be done in preparation to unify all deep link handling logic on `native` since we now have two deep link cases to handle. The end goal is to have just one handler to reduce boilerplate and similar behavior across different handlers. This will also make it easy to handle a new link down the line. In this diff, I've just moved the parsing-specific functions to `lib/facts/links.js` alongside the methods that construct the links. Resolves [[ https://linear.app/comm/issue/ENG-4823/extract-link-parsing-utils-to-lib | ENG-4823 ]]

This is going to be done in preparation to unify all deep link handling logic on `native` since we now have two deep link cases to handle. The end goal is to have just one handler to reduce boilerplate and similar behavior across different handlers. This will also make it easy to handle a new link down the line. In this diff, I've just moved the parsing-specific functions to `lib/facts/links.js` alongside the methods that construct the links. Part of [[ https://linear.app/comm/issue/ENG-4810/combine-deep-link-handlers-listeners-into-one-component | ENG-4810 ]]

This is going to be done in preparation to unify all deep link handling logic on `native` since we now have two deep link cases to handle. The end goal is to have just one handler to reduce boilerplate and similar behavior across different handlers. This will also make it easy to handle a new link down the line. In this diff, I've just moved the parsing-specific functions to `lib/facts/links.js` alongside the methods that construct the links. ResolvesPart of [[ https://linear.app/comm/issue/ENG-4823/extract10/combine-deep-link-parsing-utils-to-libhandlers-listeners-into-one-component | ENG-482310 ]]