Warning in Unexpected '}' Angular universal
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 20/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- angular, css, typescript
- Domain
- frontend
Research direction
Start by reproducing the Angular Universal compilation with Angular 5.2.4, Angular CLI 1.7.4, Library 4.0.0-beta.2, and css-star-rating 1.1.3. Inspect the generated or imported styles associated with the reported line ranges and compare the build output with a current dependency setup; done means the unexpected-brace and invalid CSS warnings no longer appear.
Written by the indexing model from the issue text.
Description
I'm submitting a...
[x] Bug report
[ ] Feature request
Current behavior
Hello I have problems when compiling with universal angle I get the following, please your help, thank you very much
WARNING in Unexpected '}' at 458:0.
WARNING in Unexpected '}' at 466:0.
WARNING in Unexpected '}' at 474:0.
WARNING in Unexpected '}' at 482:0.
WARNING in Invalid property name 'svg {
fill' at 452:2. Ignoring.
WARNING in Invalid selector '}
.rating.color-ok .star-container .star' at 458:0. Ignoring.
WARNING in Invalid property name 'svg {
fill' at 460:3. Ignoring.
WARNING in Invalid selector '}
.rating.color-positive .star-container .star' at 466:0. Ignoring.
WARNING in Invalid property name 'svg {
fill' at 468:3. Ignoring.
WARNING in Invalid selector '}
.rating.color-default .star-container .star' at 474:0. Ignoring.
WARNING in Invalid property name 'svg {
fill' at 476:3. Ignoring.
WARNING in Invalid selector '}
.rating' at 482:0. Ignoring.
Environment
Library version: 4.0.0-beta.2
css-star-rating: 1.1.3
Angular version: 5.2.4
Angular-cli: 1.7.4
Browser:
- [x ] Chrome (desktop) version XX
- Dominant language
- TypeScript
- Stars
- 219
- Forks
- 82
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from BioPhoton/angular-star-rating
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
BioPhoton/angular-star-rating#128 · 3 reactions ·
-
type: feature
Difficulty 2/5 1-3 hours Newbie friendliness 42/100
BioPhoton/angular-star-rating#126 · 2 comments · 2 reactions ·
-
type: question
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
BioPhoton/angular-star-rating#113 · 2 comments ·
-
type: feature
Difficulty 3/5 1-2 days Newbie friendliness 35/100
BioPhoton/angular-star-rating#111 · 5 reactions ·
-
type: bug
Difficulty 3/5 1-2 days Newbie friendliness 35/100
BioPhoton/angular-star-rating#108 · 1 comment ·
All issues in BioPhoton/angular-star-rating
Similar issues
-
a10y a10y-audit ai-driven-qa claude
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
linagora/twake-directory-manager#219 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
Maintainers usually reply within 1 day
-
0️⃣ phase/new
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Pulse v7: buildPreferencesFromTelos() bypasses telosSectionOrFile(), renders empty on unified-TELOS installsPossibly taken @zephyr91 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
danielmiessler/LifeOS#2393 ·
Maintainers usually reply within 4 days