Skip to content

Commit 49d407f

Browse files
authored
Merge pull request #96 from SJLennon/main
Overhaul the Help and Support section
2 parents c0dab05 + 9ee7651 commit 49d407f

10 files changed

Lines changed: 38 additions & 22 deletions

File tree

.astro/astro/content.d.ts

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -603,5 +603,5 @@ declare module 'astro:content' {
603603

604604
type AnyEntryMap = ContentEntryMap & DataEntryMap;
605605

606-
export type ContentConfig = typeof import("../../src/content/config.js");
606+
export type ContentConfig = typeof import("./../../src/content/config.js");
607607
}

.astro/settings.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
{
22
"_variables": {
3-
"lastUpdateCheck": 1756490224047
3+
"lastUpdateCheck": 1773776142351
44
}
55
}

src/assets/help_01.png

3.07 KB
Loading

src/assets/help_03.png

65.8 KB
Loading

src/assets/help_04.png

49.4 KB
Loading

src/assets/help_05.png

32.9 KB
Loading

src/assets/help_06.png

12.6 KB
Loading

src/assets/help_07.png

7.57 KB
Loading

src/assets/help_08.png

37.3 KB
Loading

src/content/docs/help-and-support.mdx

Lines changed: 36 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ import { Aside, CardGrid, Card } from '@astrojs/starlight/components';
88

99
<Card>
1010

11-
The view `HELP AND SUPPORT` provides the initial links to get help and support, should you encounter any issues in Code for IBM i.
11+
The `HELP AND SUPPORT` view provides a link to the documentation, and links to get help and support should you encounter any issues in Code for IBM i.
1212

1313
</Card><Card>
1414

@@ -18,49 +18,65 @@ The view `HELP AND SUPPORT` provides the initial links to get help and support,
1818

1919
</CardGrid>
2020

21-
### Get started
21+
### Get started & Documentation
2222

23-
This link will open the documentation for Code for IBM i in your browser, making it easy to go directly from Code for IBM i to the information on how to use it.
23+
This link opens the documentation for Code for IBM i in your browser, making it easy to go directly from Code for IBM i to the information on how to use it.
2424

2525
### Open official Forum
2626

27-
This link will take you to the Code for IBM i discussions, where you can ask any question on how to use the product.
27+
This link takes you to the Code for IBM i discussions, where you can ask any question on how to use the product.
2828

2929
### Review Issues
3030

31-
If you encounter an issue or have a problem that you suspect may be a bug in Code for IBM i, please use this link for the [Issues section](https://github.com/codefori/vscode-ibmi/issues) in the GitHub repository, where you can see all open and closed issue reports created by the users since the start of the project.
32-
There is a good chance that your problem has been seen before and a solution or workaround found, or a fix may have been created to solve a similar problem.
31+
If you have a problem, there is a good chance that your problem has been seen before. A solution or workaround may have been found, or a fix may have been created to solve a similar problem. By reviewing the [Issues section](https://github.com/codefori/vscode-ibmi/issues) in the GitHub repository you may be able to solve your issue.
32+
33+
You can see all open or closed issues reported since the start of the project and sort them by date.
34+
35+
![](../../assets/help_03.png)
36+
37+
You can also search issues by adding text in the search bar:
38+
39+
![](../../assets/help_04.png)
3340

3441
### Report an Issue
3542

3643
<Aside type="caution">
37-
**Do not use the VS Code Issue Reporter (found in Help menu item Report Issue)!**
44+
**Do not use the VS Code Issue Reporter (found in VS Code Help menu, item Report Issue)!**
3845

3946
This issue reporter does not include the configuration and logs necessary to debug your issue, and time will be wasted while the support team will request additional information from you.
4047
</Aside>
4148

42-
If searching existing issue reports using the link above did not give you the solution to your problem, you can create a new issue report using this link.
49+
If searching existing issue reports did not give you the solution to your problem, the best way to create a new issue report is by using the `Report an Issue` link.
50+
![](../../assets/help_06.png)
51+
This link collects system information about Code for IBM i, the IBM i server and VS Code.
4352

44-
<Aside type="tip">
45-
Keep your connection to the IBM i system active when creating the issue report (to have all important system information included in the report).
46-
</Aside>
53+
It then copies this information into a Github issue and opens the issue for you to complete.
54+
55+
#### Steps to create an issue
4756

48-
When you click on `Report an Issue` in the `HELP AND SUPPORT` view, your browser will open the GitHub issues page with a template containing the following information:
49-
- Code for IBM i version, VS Code version and OS
50-
- Active extensions
51-
- Remote system information, e.g. IBM i release, TR level, CCSID, enabled features and more
52-
- Shell environment
53-
- Variants (used for CCSID troubleshooting)
54-
- Errors (the last three commands executed on the server and the result)
57+
To provide the most helpful information for the support staff, follow these steps as far as possible to report an issue:
5558

56-
You must also provide a title and thorough description of the issue with information on how to recreate the issue encountered.
59+
1. Make sure you can reproduce the issue. It is extremely difficult to debug a problem that can't be reproduced.
60+
2. If the issue is related to some source code, please provide the smallest possible source example that causes the problem and use this when reproducing the issue in the next step. Later, paste the source into the Github issue as **text**. Please do not provide this code as screen shots.
61+
3. Restart VS Code, connect to the IBM i and immediately cause the problem.
62+
4. Click the `Report an Issue` link and pick the extension on which to report the issue:
63+
![](../../assets/help_08.png)
64+
5. In the opened Github issue clearly descibe the steps to cause the problem. Paste screen shots if this helps clarify the issue.
65+
6. Go to the `OUTPUT` tab and select `Code for IBM i`. Select the complete displayed contents and then copy and paste into the Github issue.:
66+
![](../../assets/help_05.png)
67+
7. Click Create to save the issue.
5768

5869
<Aside type="danger">
5970
All issues are available to the public, so any sensitive information must be redacted before submitting the issue report!
6071
</Aside>
6172

6273
<Aside type="tip">
63-
You need to have or create a GitHub account to create an issue report.
74+
Github allows you to enter text and paste images in an issue. Generally it is not necessary to create separate documents to attach as files.
75+
![](../../assets/help_07.png)
76+
</Aside>
77+
78+
<Aside type="tip">
79+
You need to have or create a GitHub account to create an issue report. Github accounts are free.
6480
</Aside>
6581

6682
### Download Logs

0 commit comments

Comments
 (0)