From 0bbb46ecc4ac067e915f0a6b414b7f88b3113a50 Mon Sep 17 00:00:00 2001 From: benjaminramey Date: Wed, 18 Sep 2024 12:47:29 -0500 Subject: [PATCH] vault backup: 2024-09-18 12:47:29 --- Daily Notes/2024/09/2024-09-18 (Wednesday).md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Daily Notes/2024/09/2024-09-18 (Wednesday).md b/Daily Notes/2024/09/2024-09-18 (Wednesday).md index fbeb0cd..c9b7020 100644 --- a/Daily Notes/2024/09/2024-09-18 (Wednesday).md +++ b/Daily Notes/2024/09/2024-09-18 (Wednesday).md @@ -11,4 +11,4 @@ A relative sick last week. Launch work? Thinks we are doing well. Any blockers? Is excited to work on new.logos.com. Has already worked on some components in next.js and it was interesting. ## [[Mitch Myers]] 1:1 -Steady person, not too much ruffles your feathers? Don't know. Working on backend changes for subscribable product bundle changes. Code changes fairly localized or spread out? Should we make an announcement to company, lots of people depend on tracks and track products. Mitch did track down usages of track products, so we are prepared for updating how those work if needed. For the most part, the code would continue working, not crash. Some places may need to be reconsidered to deal with subscribable track products. Put in your own words why this change was needed? Want to do subscriptions, show them on configuration wizard page, originally relying on tracks to point to products to point to subscribable products but that relationship is not good enough with the way we are using subscribable product bundles, so no way to tell which subscribable product was the main one to show users. Added subscribable feature set track kind. \ No newline at end of file +Steady person, not too much ruffles your feathers? Don't know. Working on backend changes for subscribable product bundle changes. Code changes fairly localized or spread out? Should we make an announcement to company, lots of people depend on tracks and track products. Mitch did track down usages of track products, so we are prepared for updating how those work if needed. For the most part, the code would continue working, not crash. Some places may need to be reconsidered to deal with subscribable track products. Put in your own words why this change was needed? Want to do subscriptions, show them on configuration wizard page, originally relying on tracks to point to products to point to subscribable products but that relationship is not good enough with the way we are using subscribable product bundles, so no way to tell which subscribable product was the main one to show users. Added subscribable feature set track kind. \ No newline at end of file