Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
refactor: typescript projects & docs generation #2804
refactor: typescript projects & docs generation #2804
Changes from 25 commits
b2b29f5
5b4729d
d2dcc36
78fb575
66e2dab
433c364
175b708
6a3648d
bc3d645
d7fe64e
8670e1f
815597c
aba2536
a75285d
55bb7b7
00b9eb3
72ed3e9
1789a99
3776b56
6fa4324
d99640a
33a5384
7eaed08
32e71c1
43cf0f1
1f056b0
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
This file was deleted.
This file was deleted.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I changed the set of build commands from
build:quick
andbuild
(which just calls the former) tobuild
(same asbuild:quick
before) andbuild:full
which makes a full typescript build, along with generated types, which I think should be in the distributed packages.This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
question(non-blocking): Interesting. So in theory when we move away from bolt in the future this would be unnecessary?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think other tools will still have this issue. The issue stems from when we run a command on "all packages" (run from the project root and have it traverse into everything including the packages), which is in contrast to running a command "per-package" (running the command in every package with that package as the root).
This difference is significant because if you start in
root/
and traverse down toroot/packages/my-package/node_modules/symlink-to-my-other-package
(a symlink) and that takes you toroot/packages/my-other-package
, you're still under the root contextroot/
which means that tooling will not look for apackage.json
file because it does not think you're checking a dependency. That is why the index file solution works, because the index file will be automatically checked when the dependency resolution thinks it's still under the root context (which is true because we chose the root to be the project, rather than a specific package).Does that make more sense?