Skip to content

Remove storage-types/exp #4507

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

Merged
merged 3 commits into from
Feb 23, 2021
Merged

Remove storage-types/exp #4507

merged 3 commits into from
Feb 23, 2021

Conversation

hsubox76
Copy link
Contributor

Remove exp types for storage as part of the effort to remove all -types packages from the exp SDK.

@changeset-bot
Copy link

changeset-bot bot commented Feb 22, 2021

⚠️ No Changeset found

Latest commit: 6ff0fa9

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

} from '@firebase/storage-types/exp';
FullMetadata,
UploadTaskSnapshot
} from './public-types';
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can directly export them instead of import, then export since ./public-types is part of the project, so we won't have the typings in the js file issues.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also can we just export every thing from ./public-types. All types in ./public-types are supposed to be public/exported.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done. A number of these types are used in this file so I kept those imports.

@@ -15,7 +15,7 @@
"lint": "eslint -c .eslintrc.js '**/*.ts' --ignore-path '../../.gitignore'",
"lint:fix": "eslint --fix -c .eslintrc.js '**/*.ts' --ignore-path '../../.gitignore'",
"build": "rollup -c rollup.config.compat.js && yarn build:exp",
"build:exp": "rollup -c rollup.config.exp.js ; yarn api-report",
"build:exp": "rollup -c rollup.config.exp.js && yarn api-report",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we want ; which executes regardless of the return status of the previous command. I believe rollup -c rollup.config.exp.js will return an error status in the exp release build, though build will go through.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, ok, restored.

@google-oss-bot
Copy link
Contributor

google-oss-bot commented Feb 23, 2021

Binary Size Report

Affected SDKs

No changes between base commit (145c62b) and head commit (8cb9427).

Test Logs

@google-oss-bot
Copy link
Contributor

google-oss-bot commented Feb 23, 2021

Size Analysis Report

Affected Products

No changes between base commit (145c62b) and head commit (8cb9427).

@hsubox76 hsubox76 merged commit 938dc1a into master Feb 23, 2021
@hsubox76 hsubox76 deleted the ch-remove-storage-types branch February 23, 2021 00:46
@firebase firebase locked and limited conversation to collaborators Mar 25, 2021
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