cps-org / cps-org/cps

Location required for component type extensions?

Open
#52 1 comment 0 reactions 0 assignees View on GitHub
documentation
Dominant language
Python
Stars
191
Forks
14
PR merge metrics
No merged PRs in 30d

Description

From the spec on component.name.type:

```
If the type is not recognized by the parser,
the component shall be ignored.
(Parsers are permitted to support additional types
as a conforming extension.)
```

From the spec on component.name.location:

```
This attribute is required for |component|\ s
that are not of :string:`"interface"` :attribute:`type`.
```

Do you think this is an intentional interaction? I am working on adding tests to our parser. Maybe `location` should be required on a closed set of specific types instead of the open set excluding `interface`?

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by comparing the component.name.type and component.name.location requirements quoted in the issue, then inspect the parser tests mentioned in the report. Resolve whether the interaction is intentional and document the chosen rule in the specification, with tests covering recognized, unrecognized, and extension component types.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.