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

add yq for year-quarter parsing #422

Closed
vspinu opened this issue Jun 16, 2016 · 6 comments
Closed

add yq for year-quarter parsing #422

vspinu opened this issue Jun 16, 2016 · 6 comments

Comments

@vspinu
Copy link
Member

@vspinu vspinu commented Jun 16, 2016

No description provided.

@hansthompson
Copy link

@hansthompson hansthompson commented Aug 3, 2016

Would this be a way having a posix-like object output from quarter()?

@vspinu
Copy link
Member Author

@vspinu vspinu commented Aug 3, 2016

What do you have in mind more concretely? You don't have to use quarter to get time-stamps. You can use floor_date(..., unit = "quarter").

For parsing I indeed had in mind returning a Date object from strings like "2016.4".

@vspinu vspinu closed this in f2f73a3 Aug 3, 2016
vspinu added a commit that referenced this issue Aug 3, 2016
@hansthompson
Copy link

@hansthompson hansthompson commented Aug 4, 2016

Yes. I was hoping this would be something that takes a string like "2016.4" and gives it a date object.

@vspinu
Copy link
Member Author

@vspinu vspinu commented Aug 4, 2016

It has been done

> yq("2014.1")
[1] "2014-01-01"

You also have a new format q that you can pass to parse_date_time and friends.

@andrewnguyen42
Copy link

@andrewnguyen42 andrewnguyen42 commented Jan 7, 2019

Could the usage for yq get added to the docs? Usage for this function isn't necessarily clear unless someone stumbles upon this issue.

@vspinu
Copy link
Member Author

@vspinu vspinu commented Jan 7, 2019

Sure. Please open a new issue for this so we don't forget about it.

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

Successfully merging a pull request may close this issue.

None yet
3 participants