-
Notifications
You must be signed in to change notification settings - Fork 21
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
[UIE-153] Create analysis package #4718
Conversation
"lib/types/**/*.d.ts" | ||
], | ||
"dependencies": { | ||
"@terra-ui-packages/components": "^0.0.6", |
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.
This points out an issue we'll have to deal with sometime where packages in the Terra UI repository can depend on older versions of Terra UI packages than the current version in the repository. I can take care of it though.
{ | ||
"extends": "../../tsconfig.base.json", | ||
"compilerOptions": { | ||
"noImplicitAny": true, |
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.
This is stricter than the Terra UI app's configuration, so some code may have to be updated when it's moved over, but I think it's well worth it.
https://www.typescriptlang.org/tsconfig#noImplicitAny
@@ -0,0 +1,49 @@ | |||
{ | |||
"name": "@terra-ui-packages/analysis", |
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.
Opinions on name? This matches the existing "analysis" folder, but could also be "interactive-analysis", etc (because interactive analysis more precisely describes the feature area, not because of the team name).
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 analysis
is fine. It's closest to the name of the tab where all the functionality lives
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.
Not super familiar with packaging, so it might be good to have another set of eyes. Looks good though, I imagine it will probably be better to iterate on these configs as we add files to the package instead of getting too hung up on the initial setup semantics
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.
love this!
A starting point for separating out interactive analysis components to be shared with AoU.