Skip to content

Improve tab_style() error messages when locations is invalid #1640

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

Merged
merged 10 commits into from
Apr 25, 2024

Conversation

olivroy
Copy link
Collaborator

@olivroy olivroy commented Apr 25, 2024

Summary

To follow-up on #1638.

I added a more user-friendly message.

I refactored the tests in c7fd52c where I added snapshot tests for errors notably to better assess messages and to create a better snapshot diff.

For review, I would recommend looking at 766f0dd. If you think wording could be improved, I will happily do so! Maybe with this PR, the resolve_rows/resolve_cols message could be simplified?

Checklist

Could relate to #1608

@olivroy olivroy changed the title Tab style/error Improve tab_style() error messages when locations is invalid Apr 25, 2024
@rich-iannone
Copy link
Member

Thank you for this. And the wording used is great here! Could you prefix any rlang fns with rlang:: (this is mostly just for consistency in the codebase).

Also, could you add yourself as an author to the authors list? You've done a lot of really excellent work here!

@rich-iannone rich-iannone self-requested a review April 25, 2024 22:56
Copy link
Member

@rich-iannone rich-iannone left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@rich-iannone rich-iannone merged commit 88d9440 into rstudio:master Apr 25, 2024
12 checks passed
@olivroy olivroy mentioned this pull request May 23, 2024
3 tasks
@olivroy olivroy deleted the tab-style/error branch June 19, 2024 19:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants