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

Fixes #301 - StepRelationshipMetadata in Step should require #302

Merged
merged 1 commit into from
Aug 24, 2020

Conversation

austinkelleher
Copy link
Contributor

RelationshipClass from @jupiterone/data-model

RelationshipClass from @jupiterone/data-model
Copy link
Contributor

@ndowmon ndowmon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How does a change to static types affect semver? Functionally its behavior is identical, so it'd be a patch... but it will now throw lint errors for existing code, so from that perspective seems like major.

@austinkelleher
Copy link
Contributor Author

@ndowmon Good question. This is a breaking change. We have not released the new version of the SDK yet. The original metadata changes haven't been released.

@ndowmon
Copy link
Contributor

ndowmon commented Aug 24, 2020

@austinkelleher Thanks for the clarification :)

@austinkelleher austinkelleher merged commit 8854ee7 into master Aug 24, 2020
@austinkelleher austinkelleher deleted the 301-relationshipclass-step branch August 24, 2020 12:57
@aiwilliams
Copy link
Contributor

That is a good question @ndowmon. I now wonder if we should be taking this approach. 🤔 Are there alternative ways to ensure the data is generated with valid relationship classes? Perhaps it should be in the schema alone?

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

Successfully merging this pull request may close these issues.

3 participants