question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Semantic versioning

See original GitHub issue

The prompt addressing of issues and corresponding releases of EntityGraphQL is wonderful, but it would be even more helpful if future releases would use Semantic Versioning to provide a heads up that a release involves breaking changes.

In 2.2.0 SchemaBuilder.GetFieldsFromObject added an autoCreateIdArguments. The additional is a good one and easy enough to update the code for. I just didn’t expect the incompatible API change.

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:6 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
lukemurraycommented, Jul 3, 2022

it is best if the field order was the same for either approach.

Good idea too!

Interesting use case and yes I think I was use the second way, I wasn’t expecting people to be using SchemaBuilder.GetFieldsFromObject 😃

Also 2.3.0 is being prepared and I do not aim to make breaking changes either (they’ll come in 3.0.0). Please let me know if you happen to see any. I’ll be reviewing the changes again before it is ready.

0reactions
breyedcommented, Jul 4, 2022

No. Definitely not worth an extra release, since the “breakage” was so minor. Going forward, I just being aware of incompatible changes to public methods, and bumping the major version number when they happen, is fine for a project this time. Keeping it simple leaves more time for working on amazing features! 😃

Read more comments on GitHub >

github_iconTop Results From Across the Web

Semantic Versioning 2.0.0 | Semantic Versioning
Remember, Semantic Versioning is all about conveying meaning by how the version number changes. If these changes are important to your users, use...
Read more >
Introduction to Semantic Versioning
Semantic versioning (also known as SemVer) is a versioning system that has been on the rise over the last few years.
Read more >
About semantic versioning
Incrementing semantic versions in published packages · Using semantic versioning to specify update types your package can accept · Resources · More videos...
Read more >
A Guide to Semantic Versioning
SemVer is a popular versioning scheme that is used by a vast amount of open-source projects to communicate the changes included in a...
Read more >
Software versioning
Software versioning is the process of assigning either unique version names or unique version numbers to unique states of computer software.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found