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

If .name_repair is a function, no repair messages are shown #763

merged 1 commit into from Apr 19, 2020


Copy link

@krlmlr krlmlr commented Apr 17, 2020

Otherwise there's no way to silence them.

Copy link

@lionel- lionel- commented Apr 17, 2020

Should this be an upstream fix?

Copy link
Member Author

@krlmlr krlmlr commented Apr 17, 2020

I think so.

@krlmlr krlmlr merged commit a22a991 into master Apr 19, 2020
13 checks passed
@krlmlr krlmlr deleted the f-632-silent-repair branch Apr 19, 2020
krlmlr added a commit that referenced this issue Feb 25, 2021
tibble 3.0.1

- `[<-.tbl_df()` coerces matrices to data frames (#762).

- Use delayed import for cli to work around unload problems in downstream packages (#754).

- More soft-deprecation warnings are actually visible.

- If `.name_repair` is a function, no repair messages are shown (#763).

- Remove superseded signal for `as_tibble.list()`, because `as_tibble_row()` only works for size 1.

- `as_tibble(validate = )` now always triggers a deprecation warning.

- Subsetting and subassignment of rows with one-column matrices work again, with a deprecation warning (#760).

- Attempts to update a tibble row with an atomic vector give a clearer error message. Recycling message for subassignment appears only if target size is != 1.

- Tweak title of "Invariants" vignette.
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 20, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet
None yet

Successfully merging this pull request may close these issues.

None yet

2 participants