Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Architecture problem: all schemas in a single dependency #170

Open
ehuelsmann opened this issue Aug 17, 2023 · 1 comment
Open

Architecture problem: all schemas in a single dependency #170

ehuelsmann opened this issue Aug 17, 2023 · 1 comment
Assignees

Comments

@ehuelsmann
Copy link
Contributor

The messages library contains two disjoint schemas:

  • Gherkin library (parser) output & test driver input (pickles)
  • Pickle runner output (test driver output)

This causes a problem for the Gherkin library, because the version numbering of Messages applies to the collected schemas. When nothing changes with respect to Gherkin, it still may need a version bump because it needs to keep pace with Messages as it is consumed by the test runners -- which gets version bumps if the input/output of the test runner schema changes.

Proposal:

The proposal is to split the messages library into multiple libraries, each publishing exactly one schema.

@luke-hill
Copy link
Contributor

@ehuelsmann - So you view it as having one library per schema per message? Or maybe one library per 3/4 schemas per 3/4 messages?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants