Add Extension Persistence Deep Dive #555
Open
+127
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Deploying contributing-docs with
|
| Latest commit: |
c339c7b
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://9a27e7b6.contributing-docs.pages.dev |
| Branch Preview URL: | https://add-persistence-deep-diave.contributing-docs.pages.dev |
|
Great job, no security vulnerabilities found in this Pull Request |
|
@willmartian @justindbaur I added you before I opened this up for wider review, and I want to make sure that I'm not wildly off base with the recommended usage. Here is the new page. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
📔 Objective
As more teams are starting to use the
ViewCacheServicefor persisting extension data, I had some feedback that it would be good to have some documentation on the framework provided by Platform to do this.This is my initial attempt at adding documentation. I'm open to any additions or clarifications, including moving it to a different area of the docs.
⏰ Reminders before review
team
🦮 Reviewer guidelines
:+1:) or similar for great changes:memo:) or ℹ️ (:information_source:) for notes or general info:question:) for questions:thinking:) or 💭 (:thought_balloon:) for more open inquiry that's not quite a confirmedissue and could potentially benefit from discussion
:art:) for suggestions / improvements:x:) or:warning:) for more significant problems or concerns needing attention:seedling:) or ♻️ (:recycle:) for future improvements or indications of technical debt:pick:) for minor or nitpick changes