## Description The evaluated values for text fields in action selector were not shown. This PR fixes the issue. #### PR fixes following issue(s) Fixes #12736 #### Type of change - Bug fix (non-breaking change which fixes an issue) ## Testing > #### How Has This Been Tested? - [x] Cypress > > #### Test Plan > Add Testsmith test cases links that relate to this PR > > #### Issues raised during DP testing > Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR) > > > ## Checklist: #### Dev activity - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my own code - [x] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [x] My changes generate no new warnings - [x] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] PR is being merged under a feature flag #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Test-plan-implementation#speedbreaker-features-to-consider-for-every-change) have been covered - [x] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans/_edit#areas-of-interest) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [x] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [x] Cypress test cases have been added and approved by SDET/manual QA - [x] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed |
||
|---|---|---|
| .. | ||
| ast | ||
| .gitignore | ||
| Readme.md | ||
Shared Dependencies
We wanted to share common logic with different applications within our repo, so we picked yarn workspaces as our approach to tackle this problem. Following are the way in which you can take advantage of the module sharing architecture.
Create a shared module
- Create a directory inside
shared - Inside the directory, create a
package.jsonfile, and set itsnamefield to@shared/<name of the module>. For example, if the module isabc, the name field should be@shared/abc. - Add the module code
- Add a
postinstallscript to build the module as needed, e.g.:
// shared/abc/package.json
{
"name": "@shared/abc",
"scripts": {
"postinstall": "rollup -c"
}
}
Install a shared module
Navigate to the directory where you want to use the module and run yarn add <module-name>.
For example, if the package.json name field is @shared/abc, run
yarn add @shared/abc