Skip to content

Commit 2e72e33

Browse files
committed
New system settings page
Signed-off-by: worksofliam <[email protected]>
1 parent f311d2e commit 2e72e33

File tree

4 files changed

+67
-2
lines changed

4 files changed

+67
-2
lines changed

.astro/astro/content.d.ts

Lines changed: 42 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -327,6 +327,41 @@ declare module 'astro:content' {
327327
collection: "docs";
328328
data: InferEntrySchema<"docs">
329329
} & { render(): Render[".mdx"] };
330+
"developing/testing/configuring.mdx": {
331+
id: "developing/testing/configuring.mdx";
332+
slug: "developing/testing/configuring";
333+
body: string;
334+
collection: "docs";
335+
data: InferEntrySchema<"docs">
336+
} & { render(): Render[".mdx"] };
337+
"developing/testing/overview.mdx": {
338+
id: "developing/testing/overview.mdx";
339+
slug: "developing/testing/overview";
340+
body: string;
341+
collection: "docs";
342+
data: InferEntrySchema<"docs">
343+
} & { render(): Render[".mdx"] };
344+
"developing/testing/running.mdx": {
345+
id: "developing/testing/running.mdx";
346+
slug: "developing/testing/running";
347+
body: string;
348+
collection: "docs";
349+
data: InferEntrySchema<"docs">
350+
} & { render(): Render[".mdx"] };
351+
"developing/testing/troubleshooting.mdx": {
352+
id: "developing/testing/troubleshooting.mdx";
353+
slug: "developing/testing/troubleshooting";
354+
body: string;
355+
collection: "docs";
356+
data: InferEntrySchema<"docs">
357+
} & { render(): Render[".mdx"] };
358+
"developing/testing/writing.mdx": {
359+
id: "developing/testing/writing.mdx";
360+
slug: "developing/testing/writing";
361+
body: string;
362+
collection: "docs";
363+
data: InferEntrySchema<"docs">
364+
} & { render(): Render[".mdx"] };
330365
"extensions/clle/index.mdx": {
331366
id: "extensions/clle/index.mdx";
332367
slug: "extensions/clle";
@@ -453,6 +488,13 @@ declare module 'astro:content' {
453488
collection: "docs";
454489
data: InferEntrySchema<"docs">
455490
} & { render(): Render[".mdx"] };
491+
"settings/system.mdx": {
492+
id: "settings/system.mdx";
493+
slug: "settings/system";
494+
body: string;
495+
collection: "docs";
496+
data: InferEntrySchema<"docs">
497+
} & { render(): Render[".mdx"] };
456498
"tips/asp.mdx": {
457499
id: "tips/asp.mdx";
458500
slug: "tips/asp";

astro.config.mjs

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -155,12 +155,12 @@ export default defineConfig({
155155
{
156156
label: 'Settings',
157157
autogenerate: { directory: 'settings/' },
158-
collapsed: false,
158+
collapsed: true,
159159
},
160160
{
161161
label: 'Extension Development',
162162
autogenerate: { directory: 'dev/'},
163-
collapsed: false,
163+
collapsed: true,
164164
}
165165

166166
],
124 KB
Loading

src/content/docs/settings/system.mdx

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
---
2+
title: System settings
3+
---
4+
5+
import { Aside } from '@astrojs/starlight/components';
6+
7+
As of Code for IBM i 2.17.0, the extension supports system-wide settings that can be configured once in the IFS, in a fixed location, and then applied to all users that connect to that system using the extension. This is useful for setting up a consistent environment across multiple users or teams.
8+
9+
All configuration files related to VS Code settings should be stored under `/etc/vscode/` in the IFS.
10+
11+
![](./settings_json.png)
12+
13+
### Code for IBM i settings
14+
15+
The path is `/etc/vscode/settings.json`. The top level is a JSON object that can contain different properties. Below is a table for the first level of properties. If sub-properties are not described here, refer to the content assist while working on the file.
16+
17+
| Property | Description |
18+
| ---------- | ----------- |
19+
| `codefori` | Used to determine the connection configuration for all clients. Should not be used for UI customisation. |
20+
21+
<Aside type="note">
22+
When server-wide settings are set, they cannot be edited from the Connection Settings UI and the fields will be read-only. This is to ensure that the settings are consistent and not accidentally changed by individual users.
23+
</Aside>

0 commit comments

Comments
 (0)