Closed
Description
We now have github-actions-typing.schema.json. It's not used in any way in the action's logic, for now it's there for some other use cases (e.g. validating typings in the catalog or using it in the IDE).
We'd like to reach a point where both the schema and the action's logic 5DE2 agree with each other in terms of certain typings being valid or not.
To be done:
- refactor
validateTypingsto be able to pass the action's manifest and typings as strings, instead of having to use the file system - as a part of preparing the test cases, generate action manifests (on the fly) based on some typings
- add a test that calls
validateTypingsand uses the "good typings" and the "bad typings" test resources + typings from the catalog and some actions to assert that both mechanisms work the same way - it may be necessary to adjust one or the other mechanism - let's discuss case by case
- once both mechanisms agree, let's consider moving the schema to the root dir of the repo, to increase discoverability
CC @Vampire
Metadata
Metadata
Assignees
Labels
No labels