Michael Love

`mutate_features` and `mutate_samples` are one workaround here. https://github.com/stemangiola/tidySummarizedExperiment/pull/94

https://github.com/const-ae/tidygenomics https://github.com/keyes-timothy/tidytof

This is awesome. Let's ask @sa-lee about these three functions and why they needed a plyranges implementation.

I don't think they will be able to fix this easily. One option would be to call _plyranges_ a key tidyomics package, but not loaded with `library(tidyomics)`.

Agree. I think a few simple examples would be great. E.g. from the examples I prepared for the figure: ``` # a grouped histogram of distances from 5' of x...

``` # ~~~ see below for plyranges example ~~~ # Fix the 5' position of ranges 1 ranges_1_5p

The `|>` pipe actually doesn't allow the above usage (unlike `%>%` you can't call it within a function). To use `|>` we need to make one intermediate variable: ``` ranges2_mid...

Sure it's fine this way. Here then is the new one: ``` ranges2_mid # Fix the center of ranges 2 anchor_center() |> mutate(width=1) ranges_1 |> # Fix the 5' position...

I've also updated the base example above.

`width` is changing the width the range, where `width` is a protected name like `start`, `end`, and `strand`. So if you have a range like so: ``` [======]