michaelbromley / michaelbromley/angular-wordpress-seed
not able to display post
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 309
- Forks
- 76
- PR merge metrics
- No merged PRs in 30d
Description
hi
i am getting bellow error
any idea how to solve.
`Error: [$sce:itype] Attempted to trust a non-string value in a content requiring a string: Context: html
http://errors.angularjs.org/1.3.20/$sce/itype?p0=html
at http://localhost/angular/build/scripts/bower_components/angular/angular.js:63:12
at trustAs (http://localhost/angular/build/scripts/bower_components/angular/angular.js:15342:15)
at Object.sce.(anonymous function) [as trustAsHtml] (http://localhost/angular/build/scripts/bower_components/angular/angular.js:16093:16)
at decorateResult (http://localhost/angular/build/scripts/app/common/services/BlogService.js:55:31)
at http://localhost/angular/build/scripts/app/common/services/BlogService.js:40:32
at Array.map (native)
at http://localhost/angular/build/scripts/app/common/services/BlogService.js:39:47
at processQueue (http://localhost/angular/build/scripts/bower_components/angular/angular.js:13318:27)
at http://localhost/angular/build/scripts/bower_components/angular/angular.js:13334:27
at Scope.$eval (http://localhost/angular/build/scripts/bower_components/angular/angular.js:14570:28)`
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start in app/common/services/BlogService.js, especially decorateResult around lines 39-55, and reproduce the reported AngularJS $sce:itype error when loading a post. Trace the value passed to trustAsHtml and confirm that posts can be displayed without the error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angularjs, javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100