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

[RFC]: improve README examples in namespace packages #1329

Closed
3 tasks done
kgryte opened this issue Feb 21, 2024 · 5 comments
Closed
3 tasks done

[RFC]: improve README examples in namespace packages #1329

kgryte opened this issue Feb 21, 2024 · 5 comments
Labels
Accepted RFC feature request which has been accepted. difficulty: 1 Low degree of difficulty. Should be straightforward to implement and/or resolve. Documentation Improvements, additions, or changes to documentation. Good First Issue A good first issue for new contributors! JavaScript Issue involves or relates to JavaScript. priority: Normal Normal priority concern or feature request. RFC Request for comments. Feature requests and proposed changes.

Comments

@kgryte
Copy link
Member

kgryte commented Feb 21, 2024

Description

This RFC proposes improving README examples in namespace packages. Currently, namespace package READMEs only include minimal examples which are not particularly informative and do not showcase namespace functionality. For example, see @stdlib/array.

Historically, namespace examples were not given much effort due to the rapidly changing nature of the project; however, now that development and organization has settled, it would be good to revisit these packages and add proper examples to better communicate to users how to use namespace contents.

For those wanting to contribute to this issue, you can use the following steps:

  • Browse through the stdlib codebase and identify namespaces having only minimal README examples (e.g., start from the root directory: https://github.com/stdlib-js/stdlib/tree/64931c5fdb4abc3a339b619658d3b5acc089e556/lib/node_modules/%40stdlib)
  • Leave a message on this issue letting project maintainers know that you are planning on updating a particular namespace README.
  • After identifying a namespace README needing updates, update the README for that namespace and that namespace only and open a PR.
  • When updating the README, examples should follow existing project conventions (e.g., ES5).
  • Examples may require functionality from other packages to help make examples more interesting.

Related Issues

None.

Questions

No.

Other

No.

Checklist

  • I have read and understood the Code of Conduct.
  • Searched for existing issues and pull requests.
  • The issue name begins with RFC:.
@kgryte kgryte added RFC Request for comments. Feature requests and proposed changes. Feature Issue or pull request for adding a new feature. Documentation Improvements, additions, or changes to documentation. Good First Issue A good first issue for new contributors! labels Feb 21, 2024
@vr-varad

This comment was marked as outdated.

@vr-varad

This comment was marked as off-topic.

@kgryte

This comment was marked as outdated.

@kgryte kgryte added difficulty: 1 Low degree of difficulty. Should be straightforward to implement and/or resolve. priority: Normal Normal priority concern or feature request. JavaScript Issue involves or relates to JavaScript. Accepted RFC feature request which has been accepted. and removed Feature Issue or pull request for adding a new feature. labels Feb 23, 2024
@Tufailahmed-Bargir
Copy link
Contributor

Tufailahmed-Bargir commented Mar 21, 2024

i am interested in doing this , please assign this to me

@kgryte
Copy link
Member Author

kgryte commented Mar 21, 2024

@Tufailahmed-Bargir We've since added individual issues for both documentation and code contributions. I suggest searching for another individual issue to pursue.

@kgryte kgryte closed this as completed Jul 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Accepted RFC feature request which has been accepted. difficulty: 1 Low degree of difficulty. Should be straightforward to implement and/or resolve. Documentation Improvements, additions, or changes to documentation. Good First Issue A good first issue for new contributors! JavaScript Issue involves or relates to JavaScript. priority: Normal Normal priority concern or feature request. RFC Request for comments. Feature requests and proposed changes.
Projects
None yet
Development

No branches or pull requests

3 participants