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.

Sign up for GitHub

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

Jump to bottom

Tracking Issue for Example Repositories #491

Closed
nxsaken opened this issue May 27, 2024 · 0 comments
Closed

Tracking Issue for Example Repositories #491

nxsaken opened this issue May 27, 2024 · 0 comments
Labels
A-important High-impact, important change E-examples Examples in the form of code snippets or word problems M-epic Issues/PRs that depend on other items (e.g. tracking issues)

Comments

@nxsaken
Copy link
Contributor

nxsaken commented May 27, 2024 •
edited
Loading

SDK examples should be moved to separate repositories, with the documentation only referencing the relevant code snippets instead of containing inlined ones.

IMO, each SDK should get its own repository instead of putting everything into a single one. This should simplify both usage and maintenance. As a language user, I want to clone only the relevant SDK examples without the rest, and run the examples "natively". As an Iroha maintainer, I want to update example repositories independently of each other to make better use of branching, tags, issues, etc.

Tracking sub-issues
@nxsaken nxsaken added the M-epic Issues/PRs that depend on other items (e.g. tracking issues) label May 27, 2024
@nxsaken nxsaken mentioned this issue May 27, 2024
Closed
@nxsaken nxsaken changed the title Tracking issue for the example repository Tracking issue for the example repositories May 27, 2024
@nxsaken nxsaken changed the title Tracking issue for the example repositories Tracking Issue for Example Repositories May 27, 2024
@nxsaken nxsaken added the E-examples Examples in the form of code snippets or word problems label May 27, 2024
@nxsaken nxsaken pinned this issue May 27, 2024
@nxsaken nxsaken added the A-important High-impact, important change label May 27, 2024
@nxsaken nxsaken closed this as not planned Won't fix, can't repro, duplicate, stale Oct 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-important High-impact, important change E-examples Examples in the form of code snippets or word problems M-epic Issues/PRs that depend on other items (e.g. tracking issues)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@nxsaken