Kyle F Butts

Hi Grant, I've put in a lot more effort on what I think is the superior package now: http://github.com/kylebutts/shiny.tailwind I think that would work better. Use `shiny.tailwind::use_tailwind()` which uses the...

Hi @PromiseKamanga, could you open a new issue and write the code you’re trying to run that fails. I’ll be happy to help

@ridwandse I think this is incorrect. Because something "runs" and spits out numbers does not mean it "works". The weights it reports are not correct. The bacon decomposition holds only...

Hi @perodmar, the problem (I think) is that for some of the 2x2s, your outcome variable is constant

@perodmar Probably not an easy way to do this within the package. Almost always, this should be a true error that someone accidentally passed a constant variable as the outcome...

Could you try renaming your control variables to single letter names?

This can be done more simply: ```r fixest_data(x, sample = "estimation") ```

I looked into this @lrberge and case.names does two things: 1. when y is an unnamed vector, it is equivalent to `obs(est)`. 2. when y is a named vector, it...

This feature seems at odds with the code-cells extension. For `.ipynb`, Positron and VSCode already recognizes h# headers in markdown chunks and populates the outline view with them. It does...

This is the problem: > A second issue is that when the unit option is used to include unit fixed effects, the package replaces the dependent variable with a de-meaned...