Skip to content

ui/next: fix bundling by explicitly listing files in tsconfig#6839

Merged
tamird merged 1 commit intocockroachdb:masterfrom
tamird:ui-fix-bundle
Jun 21, 2016
Merged

ui/next: fix bundling by explicitly listing files in tsconfig#6839
tamird merged 1 commit intocockroachdb:masterfrom
tamird:ui-fix-bundle

Conversation

@tamird
Copy link
Copy Markdown
Contributor

@tamird tamird commented May 21, 2016

cc @maxlang

Closes #7371.


This change is Reviewable

@maxlang
Copy link
Copy Markdown
Contributor

maxlang commented May 21, 2016

I'll let @mrtracy have the final word on tsconfig since he's dealt with it the most.

Created a PR to address the fact that we keep including changes to the generated proto files #6843

@mrtracy
Copy link
Copy Markdown
Contributor

mrtracy commented May 23, 2016

This causes problems when writing tests in editors that check for errors. You won't get automatic errors while writing test files, because they will not be part of the compilation (because the tsconfig has no notion of them).

Previously, maxlang (Max Lang) wrote…

I'll let @mrtracy have the final word on tsconfig since he's dealt with it the most.

Created a PR to address the fact that we keep including changes to the generated proto files #6843


Review status: 0 of 21 files reviewed at latest revision, all discussions resolved, all commit checks successful.


Comments from Reviewable

@tamird
Copy link
Copy Markdown
Contributor Author

tamird commented May 23, 2016

Are you sure? I'm still getting errors in my editor in test files.

@mrtracy
Copy link
Copy Markdown
Contributor

mrtracy commented May 23, 2016

It breaks both Vim and VSCode.

Previously, tamird (Tamir Duberstein) wrote…

Are you sure? I'm still getting errors in my editor in test files.


Review status: 0 of 21 files reviewed at latest revision, all discussions resolved, all commit checks successful.


Comments from Reviewable

@mrtracy
Copy link
Copy Markdown
Contributor

mrtracy commented May 23, 2016

I believe an alternative fix is to ensure that the /// <reference> to typings is present in every file.

@tamird
Copy link
Copy Markdown
Contributor Author

tamird commented May 23, 2016

Yeah, that's true, but sucks :(
On May 23, 2016 19:19, "mrtracy" notifications@github.com wrote:

I believe an alternative fix is to ensure that the /// to
typings is present in every file.


You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#6839 (comment)

@maxlang
Copy link
Copy Markdown
Contributor

maxlang commented Jun 6, 2016

What's the status of this PR?

@maxlang
Copy link
Copy Markdown
Contributor

maxlang commented Jun 7, 2016

@tamird @mrtracy ?

@tamird
Copy link
Copy Markdown
Contributor Author

tamird commented Jun 7, 2016

We should sit down and talk about this since it's IDE specific. Some editors support the extra option filesGlob that might be useful here, but we should make sure it doesn't break anyone's workflow.

@mrtracy
Copy link
Copy Markdown
Contributor

mrtracy commented Jun 21, 2016

Apparently this is no longer an issue in vscode. I have also stopped using vim, so this shouldn't be an issue for our main contributors anymore.

@maxlang
Copy link
Copy Markdown
Contributor

maxlang commented Jun 21, 2016

I support getting this in, since bundling is broken for me locally.

@maxlang
Copy link
Copy Markdown
Contributor

maxlang commented Jun 21, 2016

LGTM

@tamird
Copy link
Copy Markdown
Contributor Author

tamird commented Jun 21, 2016

OK, will do in a bit.
On Jun 21, 2016 16:44, "Max Lang" notifications@github.com wrote:

I support getting this in, since bundling is broken for me locally.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#6839 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/ABdsPJSMQqvMbIdetqWvixwfCBnlUGL3ks5qOE0XgaJpZM4Ijw7Q
.

@tamird tamird merged commit 2eba7fd into cockroachdb:master Jun 21, 2016
@tamird tamird deleted the ui-fix-bundle branch June 21, 2016 21:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants