angular2-services

问题 TypeScript File export class CompanyComponent { apiService : APIService; data : any; private companyUrl = 'http://localhost:4000/api/company/'; constructor(apiService : APIService) { this.apiService = apiService; this.getCompanies(this.companyUrl); } getCompanies(url: any){ this.data = this.apiService.GET(url).map((response :Response)=> response.json()).subscribe((response)=>{ this.data = response; console.log(this.data); }) } Response array [ {"_id":"58f61a132d44240d085ca2fa","comapny_name":

问题 I have class Layer : import {AfterViewInit, ViewChild} from 'angular2/core'; export class Layer implements AfterViewInit { @ViewChild('element') element; public canvas: HTMLCanvasElement = null; public context: CanvasRenderingContext2D = null; ngAfterViewInit() { this.canvas = this.element.nativeElement; this.context = this.canvas.getContext('2d'); } } which I will be extending with my component Lines : import {Component} from 'angular2/core'; import {Layer} from './layer'; import {Game} from

问题 I have class Layer : import {AfterViewInit, ViewChild} from 'angular2/core'; export class Layer implements AfterViewInit { @ViewChild('element') element; public canvas: HTMLCanvasElement = null; public context: CanvasRenderingContext2D = null; ngAfterViewInit() { this.canvas = this.element.nativeElement; this.context = this.canvas.getContext('2d'); } } which I will be extending with my component Lines : import {Component} from 'angular2/core'; import {Layer} from './layer'; import {Game} from

问题 Spring Rest Controller @PostMapping(consumes = MediaType.MULTIPART_FORM_DATA_VALUE) public ResponseEntity<PersonDTO> createPerson(@RequestParam("user") User personDTO, @RequestParam("file") MultipartFile[] file){ return new ResponseEntity<>(null, responseHeaders, HttpStatus.OK); } Angular Service createPerson(personClass : User, files : File[]): Observable<HttpEvent<{}>>{ let formdata: FormData = new FormData(); //Get Cities var obj = JSON.parse(JSON.stringify(personClass.city)); var myObj =

问题 I was using EventEmitter and @Output in Angular services, today one of the coleagues mentioned it's not a good practice. I found this post mentioning it's a bad practice and it seems mostly is personal opinion, and this answer is mentioning it's OK to use it. I couldn't find any official document about it, so if somebody knows an official answer for it please post. Official doc about EventEmittter 回答1: I was using EventEmitter and @Output in Angular services, today one of the coleagues

问题 I'm using AngularFire2. This is how I approached my AuthGuard service: canActivate(route: ActivatedRouteSnapshot, state: RouterStateSnapshot): boolean { this.af.auth.subscribe((auth) => { if(auth == null) { this.router.navigate(['/login']); this.allowed = false; } else { this.allowed = true; } }) return this.allowed; } The above code works, except when I visit a guarded page directly (i enter URL in browser), it doesn't load the respective component after the subscription resolves to true. In

问题 I am working on a project using Angular 4, NPM, Node.js, and the Angular CLI. I have a rather unusual need to load JSON into an Angular service (using an @Injectable ) without an HTTP request, i.e. it will always be loaded locally as part of the package, and not retrieved from a server. Everything I've found so far indicates that you either have to modify the project's typings.d.ts file or use an HTTP request to retrieve it from the /assets folder or similar, neither of which is an option for

问题 I have a service named HomeService and in that service I am setting and getting some data which is working fine. Here is the code for my service. import { Injectable } from '@angular/core'; @Injectable() export class HomeService { name:string; constructor() { } setParams(val) { this.name = val; } getParams() { return this.name; } } I am setting params in a component A and getting it in component B . What I want is to keep watching the getParams() for changing in the second component. I am

问题 I have been using angular 2 for about 2 weeks now and I love it with the exception of one thing... Services. Despite using them, to conform to society, I don't understand the point and I hope some one can explain the reasoning. Services don't do anything besides load data. Not to mention 9/10 what ever component I inject it into has to have similar functions to handle the data returned and make it usable. Another big problem I have with them is the overhead. Lets say (Following the heroes

问题 I'm trying to implement a filtering mechanism in a new Angular2 app, that would allow me to filter a list of entries in an array. The entries may have around 20 properties that could be filtered on. I have so far created a list of filters in one component and then a list component that is routed to, as a child. I then planned to pass the filters as queryParams through the router. Starting with just one filter this was fine: On the send side I had: this.router.navigate(['/findlist'],