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

Use dttm instead of time #133

Merged
merged 3 commits into from Jul 29, 2016
Merged

Use dttm instead of time #133

merged 3 commits into from Jul 29, 2016

Conversation

@hadley
Copy link
Member

@hadley hadley commented Jul 27, 2016

Because time seems a bit confusing

@codecov-io
Copy link

@codecov-io codecov-io commented Jul 27, 2016

Current coverage is 99.83% (diff: 50.00%)

Merging #133 into master will decrease coverage by 0.16%

@@           master       #133   diff @@
========================================
  Files          15         15          
  Lines         620        621     +1   
  Methods         0          0          
  Messages        0          0          
  Branches        0          0          
========================================
  Hits          620        620          
- Misses          0          1     +1   
  Partials        0          0          

Powered by Codecov. Last update 4bb2dbe...3dd73ac

@krlmlr krlmlr merged commit 36822ae into master Jul 29, 2016
0 of 3 checks passed
krlmlr pushed a commit that referenced this issue Jul 29, 2016
- Use multiply character `×` instead of `x` when printing dimensions (#126). Output tests had to be disabled for this on Windows.
- Use `dttm` instead of `time` for `POSIXt` values (#133).
- Rename `frame_data()` to `nibble()`, the former is still available as alias (#132).
krlmlr added a commit that referenced this issue Aug 26, 2016
- The `tibble.width` option is used for `glimpse()` only if it is finite (#153, @kwstat).
- New `as_tibble.poly()` to support conversion of a `poly` object to a tibble (#110).
- `add_row()` now correctly handles existing columns of type `list` that are not updated (#148).
- `all.equal()` doesn't throw an error anymore if one of the columns is named `na.last`, `decreasing` or `method` (#107, @BillDunlap).

- New `add_column()`, analogously to `add_row()` (#99).
- `print.tbl_df()` gains `n_extra` method and will have the same interface as `trunc_mat()` from now on.
- `add_row()` and `add_column()` gain `.before` and `.after` arguments which indicate the row (by number) or column (by number or name) before or after which the new data are inserted. Updated or added columns cannot be named `.before` or `.after` (#99).
- Rename `frame_data()` to `tribble()`, stands for "transposed tibble". The former is still available as alias (#132, #143).

- `add_row()` now can add multiple rows, with recycling (#142, @jennybc).
- Use multiply character `×` instead of `x` when printing dimensions (#126). Output tests had to be disabled for this on Windows.
- Back-tick non-semantic column names on output (#131).
- Use `dttm` instead of `time` for `POSIXt` values (#133), which is now used for columns of the `difftime` class.
- Better output for 0-row results when total number of rows is unknown (e.g., for SQL data sources).

- New object summary vignette that shows which methods to define for custom vector classes to be used as tibble columns (#151).
- Added more examples for `print.tbl_df()`, now using data from `nycflights13` instead of `Lahman` (#121), with guidance to install `nycflights13` package if necessary (#152).
- Minor changes in vignette (#115, @helix123).
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 10, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

3 participants