-
-
Notifications
You must be signed in to change notification settings - Fork 471
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
Inconsistent time fields #267
Comments
Another option (avoiding a breaking change) would be to at least implement helper methods similar to |
@kfoxb The reason might be that jira.Time was introduced later and not fully adjusted to all types. Would you be open to prepare such a PR to make it consistent across the library? |
I have a more general question regarding how to use/access/cast of the Time data? |
I was so sure that I tested and failed with: |
This issue has been automatically marked as stale because it has not had recent activity in the last 60 days. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
Hey, I am very sorry that this issue has been open for a long time with no final solution. We work on this project in our spare time, and sometimes, other priorities take over. This is the typical open source dilemma. However, there is news: We are kicking off v2 of this library 🚀To provide visibility, we created the Road to v2 Milestone and calling for your feedback in #489 The development will take some time; however, I hope you can benefit from the changes. What does this mean for my issue?We will work on this issue indirectly. Final wordsThanks for using this library. |
I've noticed that there are some fields on some of the types, in particular the Comment struct, that are strings instead of a jira.Time. Is there a reason for this? It would be a breaking change, but would you be open to a pull request to change these fields to be jira.Time instead?
The text was updated successfully, but these errors were encountered: