-
Notifications
You must be signed in to change notification settings - Fork 493
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
Misleading changelog for tag v1.2.0 #469
Comments
Hi @sGy1980de Thank you for reporting this. It was my mistake 🤦♂️ I'll try to merge the proper change and will fix it this weekend. My intention was to add this feature. |
Hey @pavelnikolov, happy to hear this. Really looking forward to this and let me thank for the precious work you guys do here. Bye |
Hey @pavelnikolov, any updates on that one? It did not sound like you wanted it to take so long. Anything one can help you with that one? Bye |
Hi @sGy1980de, |
OMG hope you'll be fine again asap. |
I've removed the misleading feature. I'll add it with the next release soon. Thank you for reporting. |
Hey guys,
I was really excited when I saw the first bullet point in the changelog for release v1.2.0, because I waited for this feature to come for quite some time now. Turns out, the linked issue #428 has only been closed but not merged and the feature isn't there at all, neither via dedicated argument nor via context.
Could we please just pick one approach or start a community vote which route they want to pick? It would really ease up some of our schemas and loaders if we would have this information upfront.
Please this discussion is going on for years now.
The text was updated successfully, but these errors were encountered: