Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Angular: HttpRequest.clone() - What is the difference between params and setParams?

I have an interceptor:

intercept(request, next) {
  const _id = 1
  const _token = "foo"
  return next.handle(request.clone({ 
    setParams: {
     user_id: _id,
     user_token: _token
    }
  });
}

I noticed that instead of setParams, there is a params field?

There was no insight on the Angular website docs for the HttpRequest class. It showed that they were there but there was no information.

Is params a hard override, and setParams a way to append additional Key->Value pairs to the request?

like image 972
Fallenreaper Avatar asked Jul 25 '26 08:07

Fallenreaper


1 Answers

The HttpRequest.clone() method provides an overload that supports passing an update object:

clone(update: { headers?: HttpHeaders; reportProgress?: boolean; 
  params?: HttpParams; responseType?: "arraybuffer" | "blob" | "text" | "json"; 
  withCredentials?: boolean; body?: T; method?: string; url?: string; 
  setHeaders?: { ...; }; setParams?: { ...; }; }): HttpRequest<T>
  • params - Provides the option to assign the HTTP parameters with an HttpParams instance, overwriting existing parameters in the process.
  • setParams - Provides the option to append the HTTP parameters using an object literal, where the keys are the names of the parameters to be set.

Source code for clone() method

clone(update: {
  headers?: HttpHeaders,
  reportProgress?: boolean,
  params?: HttpParams,
  responseType?: 'arraybuffer'|'blob'|'json'|'text',
  withCredentials?: boolean,
  body?: any|null,
  method?: string,
  url?: string,
  setHeaders?: {[name: string]: string | string[]},
  setParams?: {[param: string]: string};
} = {}): HttpRequest<any> {
  // For method, url, and responseType, take the current value unless
  // it is overridden in the update hash.
  const method = update.method || this.method;
  const url = update.url || this.url;
  const responseType = update.responseType || this.responseType;

  // The body is somewhat special - a `null` value in update.body means
  // whatever current body is present is being overridden with an empty
  // body, whereas an `undefined` value in update.body implies no
  // override.
  const body = (update.body !== undefined) ? update.body : this.body;

  // Carefully handle the boolean options to differentiate between
  // `false` and `undefined` in the update args.
  const withCredentials =
      (update.withCredentials !== undefined) ? update.withCredentials : this.withCredentials;
  const reportProgress =
      (update.reportProgress !== undefined) ? update.reportProgress : this.reportProgress;

  // Headers and params may be appended to if `setHeaders` or
  // `setParams` are used.
  let headers = update.headers || this.headers;
  let params = update.params || this.params;

  // Check whether the caller has asked to add headers.
  if (update.setHeaders !== undefined) {
    // Set every requested header.
    headers = Object.keys(update.setHeaders)
        .reduce((headers, name) => headers.set(name, update.setHeaders ![name]), headers);
  }

  // Check whether the caller has asked to set params.
  if (update.setParams) {
    // Set every requested param.
    params = Object.keys(update.setParams)
        .reduce((params, param) => params.set(param, update.setParams ![param]), params);
  }

  // Finally, construct the new HttpRequest using the pieces from above.
  return new HttpRequest(
      method, url, body, { params, headers, reportProgress, responseType, withCredentials, });
}
like image 91
Christopher Peisert Avatar answered Jul 27 '26 02:07

Christopher Peisert



Donate For Us

If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!