Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix encode, decode and uuid docs examples #929

Merged
merged 10 commits into from
Jan 28, 2025
Merged

Conversation

josephjclark
Copy link
Collaborator

Summary

Namespaces are missing in these examples!

AI Usage

Please disclose how you've used AI in this work (it's cool, we just want to
know!):

  • Code generation (copilot but not intellisense)
  • Learning or fact checking
  • Strategy / design
  • Optimisation / refactoring
  • Translation / spellchecking / doc gen
  • Other
  • I have not used AI

You can read more details in our
Responsible AI Policy

@josephjclark josephjclark requested a review from mtuchi January 21, 2025 14:32
@@ -40,12 +40,12 @@ export const encode = (data, options = { parseJson: true }) => {
* @param {object} options - Options.
Copy link
Collaborator

@mtuchi mtuchi Jan 23, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we add what options we support, Something like this i guess

* @param {boolean} [options.parseJson=true] - Whether to parse the decoded string as JSON.

@@ -9,13 +9,13 @@ import _ from 'lodash';
* @param {object} options - Options.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

* @param {boolean} [options.parseJson=true] - Whether to parse the encoded string as JSON.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed - thanks!

Copy link
Collaborator

@mtuchi mtuchi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The docs looks good @josephjclark
Just a tiny suggestion, can we document the supported option.
Something like this

* @param {boolean} [options.parseJson=true] - Whether to parse the decoded string as JSON.

If your happy with the language i can push the changes on this branch

@josephjclark
Copy link
Collaborator Author

I am patching common but not updating other adaptors. I think this will be OK

@josephjclark
Copy link
Collaborator Author

josephjclark commented Jan 28, 2025

hmm. That's caused a weird package lock diff because common is unlinked. Not sure I understand this.

Since this is a docs only change, I'll revert and remove the version bump.

Leaving the history because I want to keep a record of that fail

@josephjclark josephjclark merged commit 85d493a into main Jan 28, 2025
1 check passed
@josephjclark josephjclark deleted the common-base64-docs branch January 28, 2025 12:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

2 participants