Chris Barr

Nope, still has some issues. Here's the same test with **v1.8.5** now: http://plnkr.co/edit/ADRCObbB0mzgK2Pg0Okw?p=preview To recreate issues: Open that link and click the blue "launch preview in a separate window" icon...

**UPDATE:** I tried this again with version 1.8.6 (maybe 1.8.7 though? The `package.json` file has a different version number than the version in the JS file... hard to tell what...

The issue remains with latest release (1.8.10) Demo: http://plnkr.co/edit/PZJknd1UEptvtp8uEDKZ?p=preview

I don't think there is, that's not how angular works. It does have a `disabled-sticky` property now, so you could disable it until your app is ready for the element...

I don't this it support this right now, but you could always just do this manually with CSS to make it always sticky. ``` #my-element{ position: fixed: left: 10px; top:...

I think this is now fixed.

+1 for this. I have an element that I want to be sticky, unless the user doesn't want it to be. Ideally they could check a box to toggle this...

Does the `useIsNan` rule in this repo behave differently than the one distributed by TSlint? Is there some advantage to enabling 2 rules to check the same thing?

So, TSlint 5 has been released, and this project has released version 4. Both major version number updates and the `use-isnan` rule is **still being distributed**, yet it's still not...

After struggling with git-guppy for a bit I realized that this issue is why I can't get it working. We have a large & complex codebase with multiple projects, each...