-
Notifications
You must be signed in to change notification settings - Fork 53
chore: add TS support and remove hardcoded values from visual tests config #817
chore: add TS support and remove hardcoded values from visual tests config #817
Conversation
Generated by 🚫 dangerJS |
…ttps://github.com/stardust-ui/react into feat/add-ts-support-to-screener-interaction-tests
@@ -0,0 +1,13 @@ | |||
import { Dropdown, Button, List } from '../../../../../../src' |
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.
import { Dropdown, Button, List } from '../../../../../../src' | |
import { Dropdown, Button, List } from '@stardust-ui/react' |
Can we use just this?
If it requires tsconfig
, this should work:
require("ts-node").register({
project: "build/tsconfig.common.json",
});
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.
let me check..
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.
unfortunately, this doesn't help - but, actually, I would also expect that it should. Will take another look tomorrow, thank you!
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.
taking this as a general problem (import expressions like this one could be met quite often in the code), will clean up this stuff in the dedicated PR. Currently wasn't able to come up with resolution, but will spend additional time today
This PR introduces ability to consume TS modules in Screener configuration file.
This move allows to consume configuration parameters from
config
module, as well as to remove hardcoded class selectors from specs of interactive tests.