You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add link to MemoryStoreHashMap documentation for easier access (#961)
## Changes
<!-- Please summarize your changes. -->
While working with MemoryStoreHashMap, I noticed there wasn't a direct
link to its documentation. To improve accessibility, I added a link
directly below the function explanations. This addition aims to make it
easier for users to find detailed information, such as parameter
descriptions, without having to search separately.
<!-- Please link to any applicable information (forum posts, bug
reports, etc.). -->
## Checks
By submitting your pull request for review, you agree to the following:
- [X] This contribution was created in whole or in part by me, and I
have the right to submit it under the terms of this repository's open
source licenses.
- [X] I understand and agree that this contribution and a record of it
are public, maintained indefinitely, and may be redistributed under the
terms of this repository's open source licenses.
- [X] To the best of my knowledge, all proposed changes are accurate.
---------
Copy file name to clipboardExpand all lines: content/en-us/cloud-services/memory-stores/hash-map.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,6 +54,8 @@ After you get a hash map, call any of the following functions to read or write d
54
54
</tbody>
55
55
</table>
56
56
57
+
For in-depth documentation about each function, see `Class.MemoryStoreHashMap`.
58
+
57
59
<Alertseverity="warning">
58
60
All functions accessing data structures in memory stores are asynchronous network calls that might occasionally fail. You should wrap these calls in `Global.LuaGlobals.pcall()` to catch and handle errors, as shown in the code samples.
0 commit comments