zoukankan      html  css  js  c++  java
  • [Angular 2] Understanding OpaqueToken

    When using provider string tokens, there’s a chance they collide with other third-party tokens. Angular has with the concept of opaque tokens, that allow us to make whatever token we use unique, so we don’t run into collision problems. In this lesson we’ll explore how they work.

    We created a value provide like this:
     providers: [
        TodoService,
        ConsoleService,
        TranslateService,
       ,{
            provide: LoggerProvider, useFactory: (cs, ts) => {
                 return new LoggerProvider(cs, ts, true)
            },
            deps: [ConsoleService, TranslateService]
        } 
       ,{
            provide: apiUrl,
            useValue: 'http://localhost:3000/api'
        }
    ],

    It turns out that this can be problematic in case we're using, for example, a third-party library that comes with its own provider that introduces the same token.

    third-party.ts:

    export const THIRD_PARTY_PRIVODERS = [
      {
          provide: apiUrl,
          useValue: 'someurl'
      }
    ]

    So when you inject third-pary library into our app.ts:

     providers: [
        TodoService,
        ConsoleService,
        TranslateService,
       ,{
            provide: LoggerProvider, useFactory: (cs, ts) => {
                 return new LoggerProvider(cs, ts, true)
            },
            deps: [ConsoleService, TranslateService]
        } 
       ,{
            provide: apiUrl,
            useValue: 'http://localhost:3000/api'
        }
       ,THIRD_PARTY_PROVIDERS
    ], 

    Then it will rewrite our 'apiUrl' because THIRD_PARTY_PROVIDERS comes behind apiUrl.

    To solve this problem, Angular introduce OpaqueToken. 

    app.tokens.ts:

    import {OpaqueToken} from '@angular/core';
    
    export const API_URL = new OpaqueToken('apiUrl')

    Now 'API_URL' is a class instance not just a string, class instance is always unique.

    Then in app.ts:

    import {API_URL} from './app.tokens' 
    
    providers: [
        TodoService,
        ConsoleService,
        TranslateService,
       ,{
            provide: LoggerProvider, useFactory: (cs, ts) => {
                 return new LoggerProvider(cs, ts, true)
            },
            deps: [ConsoleService, TranslateService]
        } 
       ,{
            provide: API_URL,
            useValue: 'http://localhost:3000/api'
        }
       ,THIRD_PARTY_PROVIDERS
    ], 

    In DataService:

    import {LoggerProvider} from './LoggerProvider';
    import {Injectable} from '@angular/core';
    import {Http} from '@angular/core';
    import {Inject} from '@angular/core';
    import {API_URL} from './app.tokens';
    
    @Injectable
    export class TodoService{
    
        constructor(@Inject(API_URL) private apiUrl, private logger: LoggerProvider, private http: Http){ }
    
        getTodos(){
            this.logger.debug('Items', this.todos);
            return this.http.get(`${this.apiUrl}/todos`).map(res => res.json());
        }
    }

    Now we won't have conflict anymore.

    As a general rule, always create opaque tokens when using string tokens for providers. For example:

    third-party.ts:

    import {OpaqueToken} from '@angular/core';
    
    const API_URL = new OpaqueToken('apiUrl');
    const CONFIG_URL = new OpaqueToken('configUrl');
    
    export const THIRD_PARTY_PROVIDERS = [
      {
         provide: API_URL,
         useValue: 'somevalue'
      },
      {
         provide: CONFIG_URL,
         useValue: 'somevalue'
      }
    ]
  • 相关阅读:
    web框架和Django框架的初识
    外键的变种,单表的查询,多表的查询
    数据库的安装与初识
    响应式设计中几个class区别
    Velocity+Java较全教程
    Web开发基础
    AutoCompleteTextView不能使用的问题
    Http中Cookie与Set-Cookie头
    Java Web 乱码
    Karel运行环境配置
  • 原文地址:https://www.cnblogs.com/Answer1215/p/5880257.html
Copyright © 2011-2022 走看看