Douglas Parker

Results 54 issues of Douglas Parker
trafficstars

### Which @angular/* package(s) are relevant/releated to the feature request? `@angular/compiler-cli` ### Description Negating an async pipe in an `*ngIf` thrashes the layout because the pipe emits `null` immediately before...

feature
comp: compiler
insufficient votes
compiler: extended diagnostics

# 🚀 Feature request ### Command (mark with an `x`) - [X] projects ### Description In large Angular monorepo workspaces, it can sometimes be non-obvious to discover all the available...

feature
area: @angular/cli
feature: under consideration

# 🐞 Bug report ### Command - [X] update - [X] version ### Is this a regression? No ### Description I have a monorepo where I am adding an Angular...

type: bug/fix
freq1: low
severity1: confusing
area: angular/cli
2022Q3 Fixit

From downstream issue: https://github.com/angular/angular-cli/issues/16910. Using a `calc()` command with 3+ variable fallbacks seems to break the parser. For example, paste the following code into the CSS Nano playground: ```css .some-rule-lg...

bug
upstream

I have a minimal reproduction repo here: https://github.com/dgp1130/skylib-test-eval. (I'm using Linux. Windows may or may not reproduce.) TL;DR: Using `analysistest` to assert on an error message containing backticks will evaluate...

Hi, I'm trying to use `@parcel/css` to bundle CSS files, however there doesn't seem to be a way to provide a custom resolver for `@import` statements, the package appears to...

enhancement

This adds a new `bundleAsync()` function with support for a custom JavaScript resolver. A resolver which re-implements the default Rust behavior looks like: ```typescript import { promises as fs }...

From downstream issue https://github.com/cssnano/cssnano/issues/880 which is from downstream issue https://github.com/angular/angular-cli/issues/16910. Using a `calc()` command with 3+ variable fallbacks seems to break the parser. For example, paste the following code into...

bug
bad-parser

## Current Behavior The only ways to set test timeout currently are to explicitly set `jasmine.DEFAULT_TIMEOUT_INTERVAL = // ...` in JavaScript, or to add a timeout to the specific test...

Feature Request
help needed

The current debugging story of `rules_webtesting` is a bit lacking, as there seems to be no out-of-the-box tooling or suggestions for helping users debug their tests. Debugging is a critical...