Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(smooth): stop to ship smooth() as a part of default bundled operator #2512

Merged
merged 1 commit into from
Apr 3, 2017

Conversation

tetsuharuohzeki
Copy link
Contributor

BREAKING CHANGE: smooth() is not a part of Observable.prototype by default.
Please use import 'rxjs/add/operator/smooth'.

Motivation

I love software's easter egg and april fool joke.
I don't have any objections about that adding joke codes like smooth()
into our repository.

However, I strongly think we should not ship it as a part of default
bundled operator (in other words, I think it should not be loaded by
default in src/Rx.ts).

Default bundling smooth() causes these bad effects

  • Increasing the file size of user application by joke code by default
    • I don't have any objection to add an acutual useful code,
      and increase the file size of user application by it. It is user
      choise. But this is joke code. It's not essential for actual
      usecase.
    • This is not a code comment which we can remove by some minifiers.
      So this enforces to increasing file size all users who use
      import { Observable } from 'rxjs' style.

Related issue (if exists)

#2508

@tetsuharuohzeki tetsuharuohzeki force-pushed the remove-smooth-operator branch from bbcc016 to ca913ad Compare April 3, 2017 06:04
BREAKING CHANGE: `smooth()` is not a part of `Observable.prototype` by default.
Please use `import 'rxjs/add/operator/smooth'`.

Motivation
------------

I love software's easter egg and april fool joke.
I don't have any objections about that adding joke codes like `smooth()`
into our repository.

However, I strongly think we should not ship it as a part of default
bundled operator (in other words, I think it should not be loaded by
default in `src/Rx.ts`).

Default bundling `smooth()` causes these bad effects

- *__Increasing the file size of user application by joke code by default__*
  - I don't have any objection to add an acutual useful code,
    and increase the file size of user application by it. It is user
    choise. But this is joke code. It's not essential for actual
    usecase.
  - This is not a code comment which we can remove by some minifiers.
    So this enforces to increasing file size all users who use
    `import  { Observable } from 'rxjs'` style.
@tetsuharuohzeki tetsuharuohzeki force-pushed the remove-smooth-operator branch from ca913ad to aeb6a26 Compare April 3, 2017 07:04
@jayphelps
Copy link
Member

This was just an april fools joke and will be removed. It was only available in the special 5.2.1-smooth package, it won't be in the real 5.2.1

@jayphelps jayphelps mentioned this pull request Apr 3, 2017
@jayphelps
Copy link
Member

Ah ha! So I see now that npm has the latest tag set to 5.2.1-smooth so if anyone does npm install rxjs (any version) they'll get 5.2.1-smooth which isn't "ideal" but not really harmful AFAICT. Lmk if I'm missing something else. I'll try to get @benlesh to merge #2516 asap and publish a real 5.2.1

@benlesh benlesh merged commit f72b9aa into ReactiveX:master Apr 3, 2017
@benlesh
Copy link
Member

benlesh commented Apr 3, 2017

Oh... didn't think about updating the latest tag in npm. :( Welp... Not doing that again. I was only concerned about people with ^5.2.0 in there package.json... those people should be fine.

@tetsuharuohzeki tetsuharuohzeki deleted the remove-smooth-operator branch April 4, 2017 07:09
@lock
Copy link

lock bot commented Jun 6, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Jun 6, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants