benjaminramey/ObsidianJournal
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

vault backup: 2024-09-18 12:47:29

Browse Source
This commit is contained in:
Benjamin Ramey
2024-09-18 12:47:29 -05:00
parent ae3db03955
commit 0bbb46ecc4
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
Daily Notes/2024/09/2024-09-18 (Wednesday).md
View File

@@ -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.
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.