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

πŸ“ (doc) [NO-ISSUE]: Update documentation after feedbacks #483

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

mbertin-ledger
Copy link
Member

πŸ“ Description

Update documentation after reviews

❓ Context

Dev portal documentation

  • Feature:

βœ… Checklist

Pull Requests must pass CI checks and undergo code review. Set the PR as Draft if it is not yet ready for review.

  • Covered by automatic tests
  • Changeset is provided
  • Impact of the changes:
    • list of the changes

🧐 Checklist for the PR Reviewers

  • The code aligns with the requirements described in the linked JIRA or GitHub issue.
  • The PR description clearly documents the changes made and explains any technical trade-offs or design decisions.
  • There are no undocumented trade-offs, technical debt, or maintainability issues.
  • The PR has been tested thoroughly, and any potential edge cases have been considered and handled.
  • Any new dependencies have been justified and documented.

Copy link

vercel bot commented Nov 8, 2024

The latest updates on your projects. Learn more about Vercel for Git β†—οΈŽ

Name Status Preview Comments Updated (UTC)
device-sdk-ts-sample βœ… Ready (Inspect) Visit Preview πŸ’¬ Add feedback Nov 8, 2024 2:41pm
doc-device-management-kit βœ… Ready (Inspect) Visit Preview πŸ’¬ Add feedback Nov 8, 2024 2:41pm

Copy link
Contributor

github-actions bot commented Nov 8, 2024

Messages
⚠️ No changeset file found in the PR. Please add a changeset file.

Generated by 🚫 dangerJS against 66580e2

@@ -1,7 +1,7 @@
{
"docs": "Ledger Device Management Kits",
"explanations": "Explanations",
"begginers": "Begginer's guide",
"beginers": "Beginer's guide",
Copy link
Member

Choose a reason for hiding this comment

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

[TYPO] Beginner's

@@ -18,7 +18,7 @@ You can follow the migration guidelines [here](./migrations/)

## Glossary

Through all the documentation we will use some acronyme that you can find the following description :
Throughout all the documentation we will use several acronymes that you can find the following description :
Copy link
Member

Choose a reason for hiding this comment

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

[TYPO] acronyms


- `connected`: The device is connected.
- `locked`: The device is locked.
- `locked`: The device is locked. User needs to unlock it.
Copy link
Member

Choose a reason for hiding this comment

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

It's weird to add "User needs to unlock it", either you add something like "User needs to unlock it to perform operations with the DMK" (or something like that),or we remove that sentence


## Current Problems

Ledger JS libraries where initially made for **Ledger Live** applications. As Ledger Live is a pretty old project (> 7 years),
we have inevitably a big technical debt. Moreover time make that some part of the logic are today hard to understand and to maintain.

Moreover, some device behavior are not well handled by the libraries. For example, opening an application on the device will cause unexpected disconnection.
Another feedback we have learnt from partners (software wallets) is that we have a lack of simplicity in the libraries, it require low level knowledge to use them (ex: APDU concept).
Some device behavior are not well handled by the libraries, for example opening an application on the device will cause unexpected disconnection.
Copy link
Member

Choose a reason for hiding this comment

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

"not well" => "not correctly"

Copy link
Member

@valpinkman valpinkman left a comment

Choose a reason for hiding this comment

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

Few typos and some some comments but overall nice

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants