Strongly-typed GithubWorkflow
See original GitHub issueThe GithubWorkflow
class is very leaky. Let’s model the GH workflow APIs.
Issue Analytics
- State:
- Created 3 years ago
- Comments:12 (10 by maintainers)
Top Results From Across the Web
strongly-typed · GitHub Topics
A collection of extension methods providing strongly typed routing and link ... Strongly typed ORM for DynamoDB - Built with the single-table-design pattern ......
Read more >andrewlock/StronglyTypedId: A Rosyln-powered ... - GitHub
A Rosyln-powered generator for strongly-typed IDs. Contribute to andrewlock/StronglyTypedId development by creating an account on GitHub.
Read more >Strongly Typed native JS without a hard requirement ... - GitHub
strong -type allows easy type enforcement for all JS types objects and classes. It also supports type unions for multiple types, as well...
Read more >strongly-typed · GitHub Topics
Strong typed functional programming language dedicated to backend and web ... Strongly-typed collection of tools to make your Redux workflow more dynamic.
Read more >strongly-typed · GitHub Topics
C++ implementation of strong types ... Strongly-typed, dependency based application framework for code/data separation with dependency injection and data ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@gradybarrett I didn’t run into too many issues with unsupported keywords - I was working with the gitlab-ci schema, not Github WF. But where I did, I ended up having to modify the output (kind of defeats the purpose of a converter). I agree with you: none of the current converters are perfect, esp when considering the complexity of these schemas.
I think these should stay on the radar though. If a library improves to the point where all the boxes are checked for generating the types/L1 elements, it would be pretty sweet to do so. Until then, escape hatches will cover this use case just fine
Implemented by @RomainMuller