| Commit-Queue | +1 |
If you think these two getters should instead move to the AST classes themselves, I can refactor this.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Friendly ping
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Not sure how I feel about this. Why do we do this? Linter already can use it, and we can change both analyzer and linter atomically as needed. Making it official API though... Now we have to support it.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Not sure how I feel about this. Why do we do this? Linter already can use it, and we can change both analyzer and linter atomically as needed. Making it official API though... Now we have to support it.
Ah, I thought we were on a quest to make anything the linter uses live in public API, as it is an indication that it is sensible to want/use this utility if you are writing an analysis rule.
I can bring it up in the Model team meeting; it's not crucial for me, or important anytime soon.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Samuel RawlinsNot sure how I feel about this. Why do we do this? Linter already can use it, and we can change both analyzer and linter atomically as needed. Making it official API though... Now we have to support it.
Ah, I thought we were on a quest to make anything the linter uses live in public API, as it is an indication that it is sensible to want/use this utility if you are writing an analysis rule.
I can bring it up in the Model team meeting; it's not crucial for me, or important anytime soon.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Samuel RawlinsNot sure how I feel about this. Why do we do this? Linter already can use it, and we can change both analyzer and linter atomically as needed. Making it official API though... Now we have to support it.
Konstantin ShcheglovAh, I thought we were on a quest to make anything the linter uses live in public API, as it is an indication that it is sensible to want/use this utility if you are writing an analysis rule.
I can bring it up in the Model team meeting; it's not crucial for me, or important anytime soon.
Yes, lets discuss it.
Okie doke, discussed, and switched from extension to AST members proper.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
analyzer: Move errorRange utilities to public API
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |