4 |
5 | To create a new `Bay` element within the parent `VoltageLevel`
6 |
7 | - Navigate to the **Substation** editor
8 | - Select the parent **VoltageLevel** you want to add the bay to
9 | - Fill in all required value
10 | - Click on **Add**
11 |
12 | The create wizard allows to set
13 |
14 | - `name`: unique identified of the Bay in the parent `VoltageLevel`
15 | - `desc`: human readable description
16 |
17 | **Edit Bay**
18 |
19 | 
20 |
21 | To edit a `Bay` element:
22 |
23 | - Navigate to the **Substation** editor
24 | - Select the **Bay** you want to edit
25 | - Click on the **edit** button
26 | - Make the changes and click **Save**
27 |
28 | The element `Bay` has two attributes
29 |
30 | - `name`: unique identified of the Bay in the parent `VoltageLevel`
31 | - `desc`: human readable description
32 |
33 | **Remove Bay**
34 |
35 | To remove an existing `Bay` element within the parent `VoltageLevel`
36 |
37 | - Navigate to the **Substation** editor
38 | - Select the **Bay** you want to remove
39 | - Click on the **delete** button
40 |
--------------------------------------------------------------------------------
/packages/openscd/public/md/ClientLN.md:
--------------------------------------------------------------------------------
1 | A `ClientLN` is one of 3 elements that are describing connections between IEDs in a SCL file.
2 |
3 | **HowTo connect Report with ClientLNs**
4 |
5 | OpenSCD allows you to connect `ReportControl` via `ClientLN`. The starting point is the **IED** in the **Substation** editor.
6 |
7 | 
8 |
9 | - Click on an **IED**
10 | - Click on **Add connection** button
11 | - The `ClientLN` wizard open
12 | - On the left hand side you can select the `ReportControl` element(s) in the project
13 | - On the right hand side you can see all logical node in the receiving IED (client).
14 | - All so-called client logical nodes - logical nodes allocated to `AccessPoint` are sorted be be on top.
15 | - `LN0` element are sorted to be at the bottom
16 | - Click on `CONNECT`
17 |
18 | 
19 |
20 | > NOTE: When `ClientLN` connections are already present in the `Report Control` block the wizard does not close on **CONNECT**
21 |
22 | > NOTE: If the `RptEnabled` `max` attribute is smaller or equal to the `ClientLN` a connection is not possible. The `ReportControl` on the right hand side is disabled.
23 |
24 | > TIP: You can filter for several terms at same time. The space between terms is acting as a logical AND.
25 |
--------------------------------------------------------------------------------
/packages/openscd/public/md/Enumeration-EnumVal.md:
--------------------------------------------------------------------------------
1 |
2 | **Add EnumVal**
3 |
4 | You can use OpenSCD to add new `EnumVal`s to an existing `EnumType`.
5 |
6 | 
7 |
8 | 1. Navigate to the `EnumType` you want to add a `EnumVal` to open the **Edit EnumType** wizard.
9 | 2. Click on **ENUM VALUE** button in the middle of the wizard.
10 |
11 | *Settings*:
12 | 1. **ord***: Must be unique within the `EnumType`.
13 | 2. **desc**: user-defined description field
14 | 3. **value***: The enumeration value as string.
15 |
16 |
17 |
18 | **Edit EnumVal**
19 |
20 | You can edit existing `EnumVal` element to for example fix issues.
21 |
22 | 1. Navigate to the `EnumType` that contains the `EnumVal` you want to edit
23 | 2. Open the **Edit EnumType** page and click on the `EnumVal` you want to edit the **Edit Enum** wizard.
24 |
25 | *Settings*:
26 | 1. **ord***: Must be unique within the `EnumType`.
27 | 2. **desc**: user-defined description field
28 | 3. **value***: The enumeration value as string.
29 |
30 |
31 |
32 |
33 | *Example:*
34 | ```
35 | 
4 |
5 | To create a new `PowerTransformer` element within the parent `Bay`, `VoltageLevel` or `Substation`
6 |
7 | - Navigate to the **Substation** editor
8 | - Select the parent you want to add the power transformer to
9 | - Fill in all required values
10 | - Click on **Add**
11 |
12 | The create wizard allows to set
13 |
14 | - `type`: is fixed to `PTR`
15 | - `name`: unique identified of the power transformer in the parent
16 | - `desc`: human readable description
17 |
18 | **Edit PowerTransformer**
19 |
20 | 
21 |
22 | To edit a `PowerTransformer` element:
23 |
24 | - Navigate to the **Substation** editor
25 | - Select the **PowerTransformer** you want to edit
26 | - Click on the **edit** button
27 | - Make the changes and click **Save**
28 |
29 | The element `PowerTransformer` has two attributes
30 |
31 | - `name`: unique identified of the Bay in the parent
32 | - `desc`: human readable description
33 | - `type`: fixed to `PTR`
34 |
35 | **Remove PowerTransformer**
36 |
37 | To remove an existing `PowerTransformer` element within the parent `Bay`
38 |
39 | - Navigate to the **Substation** editor
40 | - Select the **PowerTransformer** you want to remove
41 | - Click on the **delete** button
42 |
--------------------------------------------------------------------------------
/packages/openscd/public/md/Project-workflow.md:
--------------------------------------------------------------------------------
1 | This page is related to topics concerning project workflow within **OpenSCD**. One of the basic goals of **OpenSCD** is to save the information in the project exclusivity to SCL files and while doing so to avoid `private` elements where possible. To be more precise we try to avoid to put information to namespaces that are not defined by the standard. This shall ensure the likelihood for interoperability in multi vendor projects. Avoiding `private` element does not mean that OpenSCD removes any. In fact for the time being OpenSCD just ignores private section.
2 |
3 | As all information in **OpenSCD** are saved to SCL files and not some proprietary file formats a project is equal to a SCL file.
4 |
5 | ### Create new project
6 | 1. Open **OpenSCD**
7 | 2. Click on **New project**
8 |
9 | ### Open project
10 | 1. Navigate to the **Menu**
11 | 2. Click **Open project**
12 |
13 | > NOTE: You can open any kind of SCL type.
14 |
15 | ### Import information from other SCL files
16 | See more information in [Import IEDs](https://github.com/openscd/open-scd/wiki/Import-IEDs)
17 |
18 | ### Save project
19 |
20 | See more information in [Save project to SCL](https://github.com/openscd/open-scd/wiki/Save-project)
--------------------------------------------------------------------------------
/packages/openscd/public/md/Save-project.md:
--------------------------------------------------------------------------------
1 | One of the things that user might be different in OpenSCD compared to a desktop application is **Save project**. As OpenSCD runs in the browser we use the browser standard behavior to save files and in most browsers this means that the file is downloaded in the download folder on your machine directly.
2 |
3 | HOWEVER, you can change this standard behavior. In Chrome and Chromium, this setting is called **Ask where to save each file before downloading**.
--------------------------------------------------------------------------------
/packages/openscd/public/md/Substation-Section-Basics.md:
--------------------------------------------------------------------------------
1 | The so-called substation section does have two variants of element. The first one we will refer to as process type elements or process structure that allow to create the physically visible structure in the substation. This process structure consists of the elements:
2 |
3 | - [Substation](https://github.com/openscd/open-scd/wiki/Substation)
4 | - [Voltage Level](https://github.com/openscd/open-scd/wiki/Voltage-Level)
5 | - [Bay](https://github.com/openscd/open-scd/wiki/Bay)
6 | - [Conducting Equipment](https://github.com/openscd/open-scd/wiki/Conducting-Equipment)
7 | - `General Equipment` (not yet implemented)
8 | - [Conducting Equipment](https://github.com/openscd/open-scd/wiki/Power-Transformer)
9 | - `Transformer Winding` (not yet implemented)
10 | - `Neutral Winding` (not yet implemented)
11 | - `Line` (not yet implemented)
12 | - `Process` (not yet implemented)
13 |
14 | the other type of elements we call function type elements or functional structure that consist of the following elements:
15 |
16 | - [Function](https://github.com/openscd/open-scd/wiki/Function)
17 | - [SubFunction](https://github.com/openscd/open-scd/wiki/Function)
18 | - [EqFunction](https://github.com/openscd/open-scd/wiki/Function)
19 | - [EqSubFunction](https://github.com/openscd/open-scd/wiki/Function)
20 |
--------------------------------------------------------------------------------
/packages/openscd/public/md/Substation.md:
--------------------------------------------------------------------------------
1 | **Create Substation**
2 |
3 | 
4 |
5 | To create a new `Substation` element within the SCL root element
6 |
7 | - Navigate to the **Substation** editor
8 | - Click on the **Add mode** button on the upper right of the editor pane
9 | - Fill in all required value
10 | - Chose if the [substation structure shall be created automatically](https://github.com/openscd/open-scd/wiki/Guess-substation-structure)
11 | - Click on **Add**
12 |
13 | The create wizard allows to set
14 |
15 | - `name`: unique identified of the substation in the SCL root element
16 | - `desc`: human readable description
17 |
18 | **Edit Substation**
19 |
20 | 
21 |
22 | To edit a `Substation` element:
23 |
24 | - Navigate to the **Substation** editor
25 | - Select the **Substation** you want to edit
26 | - Click on the **edit** button
27 | - Make the changes and click **Save**
28 |
29 | The element `Substation` has two attributes
30 |
31 | - `name`: unique identified of the substation in the SCL root element
32 | - `desc`: human readable description
33 |
34 | **Remove Substation**
35 |
36 | To remove an existing `Substation` element within the SCL root element
37 |
38 | - Navigate to the **Substation** editor
39 | - Select the **Substation** you want to remove
40 | - Click on the **delete** button
41 |
--------------------------------------------------------------------------------
/packages/openscd/public/md/Validate-schema.md:
--------------------------------------------------------------------------------
1 | Schema validation is the most important validation tool. It is crucial to make sure that there are no schema related issues latest on saving the project, as the schema defines the SCL structure it therefore ensures interoperability and should be a minimal requirement.
2 |
3 | Under the hood we are using the industry standard to do schema validation [libxml2](https://en.wikipedia.org/wiki/Libxml2). The external library can be used by other web based tools as well. We have create another repository [xmlvalidate.js](https://github.com/openscd/xmlvalidate.js) that allows you to use the schema validation.
4 |
5 | The results/issues are show in the **diagnostics** pane and als important when there are no issues and the schema validation is successful. This at the end what you want to see :).
--------------------------------------------------------------------------------
/packages/openscd/public/md/Validators.md:
--------------------------------------------------------------------------------
1 | Validators are the backbone of this editor. It is very tricky to handle the complexity of an SCL file without it. This is especially true for people just working with SCL files and OpenSCD. In most cases, we try to avoid producing invalid files, but especially in **expert mode**, it is not always possible.
2 |
3 | There are two validation functions implemented at the moment. Both are triggered on opening an project or creating a new project. So every time the project basis change. And all validators are triggered on every editor action. That means every time there are changes in the project basis. All results are displayed in the **diagnostics** pane (Ctrl D) and are group by the validation function
4 |
5 |
6 | 1. [Schema validator](https://github.com/openscd/open-scd/wiki/Validate-schema)
7 | 2. [Templates validator](https://github.com/openscd/open-scd/wiki/Validate-template)
--------------------------------------------------------------------------------
/packages/openscd/public/md/XML-code-editor.md:
--------------------------------------------------------------------------------
1 |
2 | With **OpenSCD** elements are manipulated with so-called wizard pages. If such a page has not been created yet for an element you want to manipulate or you just are curious how this element looks like in the XML we have added a **pro mode** that you can select in **Settings**
3 |
4 | 
5 |
6 | 1. Open **Menu**
7 | 2. Click on **Setting**
8 | 3. Click on switch **pro mode**
9 |
10 |
11 |
12 | Once this is done you can open any wizard page e.g. **Edit Substation**. You can see a toggle button on the upper right corner. If you click this toggle button the wizard page disappears and the XML code editor appear containing the element in raw XML.
13 |
14 | 
15 |
16 | > NOTE: This is a feature for experienced users. You can also use this feature to change SCL content. Behind the scenes the element will be exchanged completely with the updated version. Of course you can undo anytime.
17 |
18 |
19 |
20 |
--------------------------------------------------------------------------------
/packages/openscd/public/xml/CC-EULA.pdf:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/openscd/open-scd/dd6e5507d4dc9c96f7410105cd4622b82c55c43f/packages/openscd/public/xml/CC-EULA.pdf
--------------------------------------------------------------------------------
/packages/openscd/public/xml/Disclaimer.md:
--------------------------------------------------------------------------------
1 | **CC-EULA License Requirement**: The files within this directory are subject to the CC-EULA (Creative Commons End User License Agreement) license. Users are required to adhere to the terms and conditions specified in the CC-EULA for the use, distribution, and modification of these files.
2 |
3 | **NSD Files (IEC Code Components) Unmodified**: It is hereby stated that no modifications have been made to the NSD files (IEC Code Components) in this directory. Users are expected to utilize these files in their original form as provided.
4 |
5 | **Modification Restrictions for NSD Files**: In the event that modifications to the NSD files are necessary, it is imperative that any changes comply with the guidelines established by the IEC relevant working groups (TC57). Unauthorized modifications are strictly prohibited. Changes must be submitted through the appropriate channels within the IEC working groups.
6 |
7 | **Applicability to Maintainers, Contributors, and Downstream Users**: These notes apply to maintainers, contributors, and external downstream users of the files within this directory. All individuals and entities interacting with these files are bound by the specified license and guidelines, and any deviations from these terms are not permitted.
8 |
9 | Please ensure strict adherence to these conditions to maintain the integrity of the files and compliance with the relevant licensing and standards.
10 |
--------------------------------------------------------------------------------
/packages/openscd/src/WizardDivider.ts:
--------------------------------------------------------------------------------
1 | import {
2 | css,
3 | customElement,
4 | html,
5 | LitElement,
6 | property,
7 | TemplateResult,
8 | } from 'lit-element';
9 |
10 | @customElement('wizard-divider')
11 | export class WizardDividerElement extends LitElement {
12 | @property({
13 | type: String,
14 | })
15 | header?: string;
16 |
17 | render(): TemplateResult {
18 | return html` ${this.renderHeader()} ${this.renderSeparator()}`;
19 | }
20 |
21 | private renderHeader(): TemplateResult {
22 | if (!this.header) {
23 | return html``;
24 | }
25 |
26 | return html`${this.header}
`; 27 | } 28 | 29 | private renderSeparator(): TemplateResult { 30 | return html``; 31 | } 32 | 33 | static styles = css` 34 | div { 35 | height: 0px; 36 | margin: 10px 0px 10px 0px; 37 | border-top: none; 38 | border-right: none; 39 | border-left: none; 40 | border-image: initial; 41 | border-bottom: 1px solid rgba(0, 0, 0, 0.12); 42 | } 43 | `; 44 | } 45 | -------------------------------------------------------------------------------- /packages/openscd/src/addons/editor/edit-v1-to-v2-converter.ts: -------------------------------------------------------------------------------- 1 | import { Edit, EditV2, isComplex, isInsert, isNamespaced, isRemove, isUpdate, Update } from '@openscd/core'; 2 | 3 | export function convertEditV1toV2(edit: Edit): EditV2 { 4 | if (isComplex(edit)) { 5 | return edit.map(convertEditV1toV2); 6 | } else if (isRemove(edit)) { 7 | return edit as EditV2; 8 | } else if (isInsert(edit)) { 9 | return edit as EditV2; 10 | } else if (isUpdate(edit)) { 11 | return convertUpdate(edit); 12 | } else { 13 | throw new Error('Unknown edit type'); 14 | } 15 | } 16 | 17 | function convertUpdate(edit: Update): EditV2 { 18 | const attributes: Partial
7 |
8 |
9 |
10 |
11 | test label
12 |
16 |
17 |
18 |
19 |
20 |
21 |
28 |
29 |
30 |
31 | edit
32 |
33 |
34 |
35 | test label
36 |
40 |
41 |
42 |
43 |
44 |
45 |
6 |
7 |
12 |
13 |
14 |
15 |
16 |
17 |
18 |
19 | -
23 |
${this.elementNames.join(' / ')}
31 | `; 32 | } 33 | 34 | static styles = css` 35 | h3 { 36 | color: var(--mdc-theme-on-surface); 37 | font-family: 'Roboto', sans-serif; 38 | font-weight: 300; 39 | overflow: hidden; 40 | white-space: nowrap; 41 | text-overflow: ellipsis; 42 | margin: 0px; 43 | line-height: 48px; 44 | padding-left: 0.3em; 45 | transition: background-color 150ms linear; 46 | }`; 47 | } 48 | -------------------------------------------------------------------------------- /packages/plugins/src/editors/protocol104/base-container.ts: -------------------------------------------------------------------------------- 1 | import { LitElement, property } from 'lit-element'; 2 | 3 | export class Base104Container extends LitElement { 4 | @property() 5 | doc!: XMLDocument; 6 | @property({ type: Number }) 7 | editCount = -1; 8 | } 9 | -------------------------------------------------------------------------------- /packages/plugins/src/editors/singlelinediagram/wizards/bay.ts: -------------------------------------------------------------------------------- 1 | import { TemplateResult } from 'lit-element'; 2 | import { get } from 'lit-translate'; 3 | 4 | import { Wizard } from '@openscd/open-scd/src/foundation.js'; 5 | 6 | import '@openscd/open-scd/src/wizard-textfield.js'; 7 | import { renderBayWizard } from '../../../wizards/bay.js'; 8 | import { 9 | getDescAttribute, 10 | getNameAttribute, 11 | getXCoordinateAttribute, 12 | getYCoordinateAttribute, 13 | updateNamingAndCoordinatesAction, 14 | renderXYCoordinateFields, 15 | } from './foundation.js'; 16 | 17 | function render( 18 | name: string | null, 19 | desc: string | null, 20 | xCoordinate: string | null, 21 | yCoordinate: string | null 22 | ): TemplateResult[] { 23 | return renderBayWizard(name, desc).concat( 24 | renderXYCoordinateFields(xCoordinate, yCoordinate) 25 | ); 26 | } 27 | 28 | export function editBayWizard(element: Element): Wizard { 29 | return [ 30 | { 31 | title: get('bay.wizard.title.edit'), 32 | element, 33 | primary: { 34 | icon: 'edit', 35 | label: get('save'), 36 | action: updateNamingAndCoordinatesAction(element), 37 | }, 38 | content: render( 39 | getNameAttribute(element), 40 | getDescAttribute(element), 41 | getXCoordinateAttribute(element), 42 | getYCoordinateAttribute(element) 43 | ), 44 | }, 45 | ]; 46 | } 47 | -------------------------------------------------------------------------------- /packages/plugins/src/editors/subscription/goose/foundation.ts: -------------------------------------------------------------------------------- 1 | import { SubscribeStatus } from '../foundation.js'; 2 | 3 | export interface GOOSESelectDetail { 4 | gseControl: Element | undefined; 5 | dataset: Element | undefined; 6 | } 7 | export type GOOSESelectEvent = CustomEvent
8 |
13 |
14 |
15 | `;
16 | /* end snapshot Substation Plugin without a doc loaded looks like the latest snapshot */
17 |
18 |
--------------------------------------------------------------------------------
/packages/plugins/test/integration/editors/communication/__snapshots__/Communication.test.snap.js:
--------------------------------------------------------------------------------
1 | /* @web/test-runner snapshot v1 */
2 | export const snapshots = {};
3 |
4 | snapshots["Communication Plugin without a doc loaded looks like the latest snapshot"] =
5 | `
6 |
7 | [communication.missing]
8 |
9 |
14 |
15 |
16 | `;
17 | /* end snapshot Communication Plugin without a doc loaded looks like the latest snapshot */
18 |
19 |
--------------------------------------------------------------------------------
/packages/plugins/test/integration/editors/substation/__snapshots__/bay-editor-wizarding.test.snap.js:
--------------------------------------------------------------------------------
1 | /* @web/test-runner snapshot v1 */
2 | export const snapshots = {};
3 |
4 | snapshots["bay-editor wizarding integration looks like the latest snapshot"] =
5 | `
12 |
19 |
20 |
25 |
26 |
27 |
12 |
19 |
20 |
25 |
26 |
27 |
6 |
19 | `;
20 | /* end snapshot SMV Subscribe Data Binding Plugin looks like the latest snapshot */
21 |
22 |
--------------------------------------------------------------------------------
/packages/plugins/test/unit/editors/__snapshots__/GooseSubscriberLaterBinding.test.snap.js:
--------------------------------------------------------------------------------
1 | /* @web/test-runner snapshot v1 */
2 | export const snapshots = {};
3 |
4 | snapshots["SMV Subscribe Later Binding Plugin looks like the latest snapshot"] =
5 | `
7 |
11 |
12 |
16 |
17 |
18 |
6 |
19 | `;
20 | /* end snapshot SMV Subscribe Later Binding Plugin looks like the latest snapshot */
21 |
22 |
--------------------------------------------------------------------------------
/packages/plugins/test/unit/editors/__snapshots__/SMVSubscriberDataBinding.test.snap.js:
--------------------------------------------------------------------------------
1 | /* @web/test-runner snapshot v1 */
2 | export const snapshots = {};
3 |
4 | snapshots["SMV Subscribe Data Binding Plugin looks like the latest snapshot"] =
5 | `
7 |
11 |
12 |
16 |
17 |
18 |
6 |
19 | `;
20 | /* end snapshot SMV Subscribe Data Binding Plugin looks like the latest snapshot */
21 |
22 |
--------------------------------------------------------------------------------
/packages/plugins/test/unit/editors/__snapshots__/SMVSubscriberLaterBinding.test.snap.js:
--------------------------------------------------------------------------------
1 | /* @web/test-runner snapshot v1 */
2 | export const snapshots = {};
3 |
4 | snapshots["SMV Subscribe Later Binding Plugin looks like the latest snapshot"] =
5 | `
7 |
11 |
12 |
16 |
17 |
18 |
6 |
19 | `;
20 | /* end snapshot SMV Subscribe Later Binding Plugin looks like the latest snapshot */
21 |
22 |
--------------------------------------------------------------------------------
/packages/plugins/test/unit/editors/cleanup/foundation.test.ts:
--------------------------------------------------------------------------------
1 | import { expect } from '@open-wc/testing';
2 | import { identitySort } from '../../../../src/editors/cleanup/foundation.js';
3 |
4 | describe('Sorting items by their identity', () => {
5 | let doc: Document;
6 | beforeEach(async () => {
7 | doc = await fetch('/test/testfiles/cleanup.scd')
8 | .then(response => response.text())
9 | .then(str => new DOMParser().parseFromString(str, 'application/xml'));
10 | });
11 |
12 | it('returns the correct name for an element.', () => {
13 | const dataSets = doc.querySelectorAll('DataSet');
14 | const orderedDataSets = identitySort(Array.from(dataSets)).map(dataSet =>
15 | dataSet.getAttribute('name')
16 | );
17 | // verified through inspection of the identity of each element
18 | // e.g. const ids = identitySort(Array.from(datasets)).map(ds => identity(ds));
19 | expect(orderedDataSets).to.eql([
20 | 'GooseDataSet1',
21 | 'GooseDataSet2',
22 | 'LogDataSet1',
23 | 'dataSet',
24 | 'dataSet',
25 | 'GooseDataSet1',
26 | 'PhsMeas1',
27 | 'PhsMeas2',
28 | ]);
29 |
30 | });
31 | });
32 |
--------------------------------------------------------------------------------
/packages/plugins/test/unit/editors/communication/__snapshots__/conductingap-editor.test.snap.js:
--------------------------------------------------------------------------------
1 | /* @web/test-runner snapshot v1 */
2 | export const snapshots = {};
3 |
4 | snapshots["A component to visualize SCL element ConnectedAP looks like the latest snapshot"] =
5 | `
7 |
11 |
12 |
16 |
17 |
18 | 6 | IED1 / AccessPoint1 / My Little Server 7 |
8 | `; 9 | /* end snapshot element-path looks like the latest snapshot */ 10 | 11 | -------------------------------------------------------------------------------- /packages/plugins/test/unit/editors/ied/__snapshots__/ied-container.test.snap.js: -------------------------------------------------------------------------------- 1 | /* @web/test-runner snapshot v1 */ 2 | export const snapshots = {}; 3 | 4 | snapshots["ied-container looks like the latest snapshot"] = 5 | `
15 |
19 |
20 |
21 |
22 |
23 |
24 |
28 |
29 |
30 |
31 |
32 |
33 |
34 |
35 |
36 |
37 |
38 |
10 |
15 |
16 |
17 | `;
18 | /* end snapshot values-104-container SCL with IED Elements looks like the latest snapshot */
19 |
20 | snapshots["values-104-container SCL without IED Elements looks like the latest snapshot"] =
21 | `22 | 23 | [protocol104.values.missing] 24 | 25 |
26 |
27 |
32 |
33 |
34 | `;
35 | /* end snapshot values-104-container SCL without IED Elements looks like the latest snapshot */
36 |
37 |
--------------------------------------------------------------------------------
/packages/plugins/test/unit/editors/protocol104/subnetwork-container.test.ts:
--------------------------------------------------------------------------------
1 | import { html, fixture, expect } from '@open-wc/testing';
2 |
3 | import '../../../../src/editors/protocol104/subnetwork-container.js'
4 | import { SubNetwork104Container } from '../../../../src/editors/protocol104/subnetwork-container.js';
5 |
6 | describe('subnetwork-104-container', () => {
7 | let element: SubNetwork104Container;
8 | let subNetwork: Element;
9 |
10 | beforeEach(async () => {
11 | const validSCL = await fetch('/test/testfiles/104/valid-subnetwork.scd')
12 | .then(response => response.text())
13 | .then(str => new DOMParser().parseFromString(str, 'application/xml'));
14 |
15 | subNetwork = validSCL.querySelector('SubNetwork[name="F1"]')!;
16 | element =
12 |
13 |
14 |
15 |
12 |
19 |
20 |
26 |
27 |
32 |
33 |
38 |
39 |
40 | 7 | [subscription.goose.publisher.subscriberTitle] 8 |
9 |7 | [subscription.smv.publisher.subscriberTitle] 8 |
9 |
12 |
13 |
14 |
15 |
16 |
21 |
22 |
27 |
28 |
35 |
36 |
42 |
43 |
44 |
12 |
20 |
21 |
28 |
29 |
30 |
12 |
13 |
14 |
15 |
12 |
19 |
20 |
27 |
28 |
33 |
34 |
35 |
12 |
20 |
21 |
28 |
29 |
36 |
37 |
38 |
12 |
17 |
18 |
23 |
24 |
29 |
30 |
35 |
36 |
41 |
42 |
43 |