Conversation
CallWithChat bundle size is not changed.
|
Chat bundle size is not changed.
|
Calling bundle size is not changed.
|
@azure/communication-react jest test coverage for beta.
|
@azure/communication-react jest test coverage for stable.
|
| packages/communication-react/temp/communication-react.api.json | ||
|
|
||
| jest-test-coverage: | ||
| needs: [get_matrix, build_packages] |
There was a problem hiding this comment.
As this job has its own build step, we don't need to wait for build_packages job to be completed
There was a problem hiding this comment.
We don't need it, this is true. But there's no point running it unless the build step completes successfully
There was a problem hiding this comment.
Build job also includes linting and treeshaking (~2 minutes) that can be skipped for tests. Tests will finish or almost will finish their run during that time.
Or are we going to move those too out of the build job?
There was a problem hiding this comment.
These aren't the critical path, so it doesn't really matter how long these tests take to run.
Yes, building also does linting too.
I tried moving that out to a pre-build job, but it doesn't make the process quicker.
| uses: actions/setup-node@v4 | ||
| with: | ||
| node-version: '20.x' | ||
| node-version: 'lts/*' |
There was a problem hiding this comment.
I'm hesitant about using LTS on anything CI where we should be as stable as possible and try pinning dependencies that may shift under us. We will hit those issues where suddenly half the PRs start failing or snapshots are partially updating if the linux version bump has some big changes.
Is the purpose to improve performance (prevent the linux machines from having to take time installing the right version)? (If so, how much does it improve by? i.e. to evaluate if its worth it)
There was a problem hiding this comment.
I understand we want to control the deps as much as possible.
For the case of CI though, we should be using LTS node regardless. This change keeps it in sync.
The purpose for this change is so we don't need as much maintenance time. This will always use LTS.
There was a problem hiding this comment.
As an aside, we could also make this a matrix and run the whole thing against multiple node versions...
There was a problem hiding this comment.
For the case of CI though, we should be using LTS node regardless
Why is this? I feel we shouldn't be using LTS for CI. At all times we should have a stable development platform that devs know will work and can contribute changes that remains unblocked. Separate from that, we then upgrade our development contract when new versions of node are LTS only after we've verified new versions work.
I would definitely be in favor of action though that is kicked off nightly/automatically when we new versions of node are released and verifies CI works.
There was a problem hiding this comment.
The crux here is that LTS will migrate the node version as LTS roles automatically, which means there's no way it will get forgotten. It means one less thing to update.
If we're not running CI against the LTS version of Node, what do you feel we should be using and why?
If we're keeping on top of dependencies internally, then there will never be an issue. If, however, there does happen to be a break when a new version of node comes out and we have not been ready for it, we have a means to ensure it is caught.
| - name: Type check test folder | ||
| if: ${{ matrix.flavor == 'beta' }} | ||
| run: cd packages/react-composites && rushx tsc:e2e | ||
| # # Type check test folder |
There was a problem hiding this comment.
This can probably be deleted.
The job is not run within a matrix context, so the test here is always false and does not get executed. Need to confirm this was the intention
|
Failed to pass the UI Test. If this PR is for UI change and the error is snapshot mismatch, please add "update_snapshots" label to the PR for updating the snapshot. |
* [Calling sounds] Stabilize Calling sounds feature (#3969) * stabilize sounds * Change files * Duplicate change files for beta release * build beta API * fix breaking change * build API files * update stable API --------- Signed-off-by: Donald McEachern <94866715+dmceachernmsft@users.noreply.github.com> * Fix `noInvalidAny` chat composites (#3987) * [DTMF Dialler] Enable DTMF mode and dialing out mode in dialpad (#3970) * remove code forcing end of number to be edit with key * Change files * Duplicate change files for beta release * add editing mode for dialing and dtmf default * disable input on click if there is no editing * remove ref * build API * fix test for new API * [InlineImage][Test] Resolve resource not found error for inline image placeholder UITest (#3979) * Resolve resource not found error for inline image placeholder UITest * Update UI Testing doc Signed-off-by: Patrick Latter <73612854+palatter@users.noreply.github.com> * Resolve issue with inline image placeholder test * Change files * Duplicate change files for beta release --------- Signed-off-by: Patrick Latter <73612854+palatter@users.noreply.github.com> * Fix up typing on chat components (#3988) * Replace html-to-react with html-react-parser (#3995) * Enable noImplicitAny in chat-stateful-client (#3998) * Enable noImplicitAny in the chat sample (#4000) * Update component examples for noImplicitAny (#4001) * Make Calling Sample textfield validate the Teams user id format (#3967) * Prevent dialpad unecessarily triggering onChange event (#3963) * [DTMF Dialer] Update Dialpad styles per designs (#3999) * Update Dialpad styles per designs * Change files * Duplicate change files for beta release * fix alignment * Update packages/react-composites CallWithChatComposite browser test snapshots * Update packages/react-composites CallComposite browser test snapshots * sizing * Update packages/react-composites CallWithChatComposite browser test snapshots * Update packages/react-composites CallComposite browser test snapshots --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * [Calling] Send reaction button component (#3997) * Add Spotlight feature to stateful call client (#3993) * Add Spotlight feature to stateful call client * Change files * Duplicate change files for beta release * update api * mark spot light feature as in progress * added code docs * Add spotlight feature selectors and handlers (#4004) * Add Spotlight feature to stateful call client * Change files * Duplicate change files for beta release * update api * mark spot light feature as in progress * update api * Add Spotlight selectors and handlers * Change files * Duplicate change files for beta release * remove ununsed import * remove duplicate handlers already in common calling handlers * memoize spotlightedParticipantIds * remove 'on' prefix from spotlight adapter functions * fix conditional compilation * added code docs * small edit * Change hidesurvey to disablesurvey based on ARB (#4006) * hide survey * Change files * Duplicate change files for beta release --------- Co-authored-by: Donald McEachern <94866715+dmceachernmsft@users.noreply.github.com> * [Calling Deps] Update to new Calling beta (#4008) * update to new Calling beta * Change files * Duplicate change files for beta release * cc new type * fix hermetic * fix test mock * Update packages/react-composites ChatComposite browser test snapshots --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Add callback when survey is dismissed for selfhost (#4009) * add callback for survey dismissed to selfhost * Change files * Duplicate change files for beta release * build files * [Calling] Send reaction component calling-component-binding and composite changes (#4003) * Add license field for package.json files (#4018) * [Chat] Remove inline image from stable (#4010) * Revert "[Chat] Remove file card group message from stable API (#3940)" This reverts commit 74a97ba. * Revert "[Chat] Rename ImageGallery related Chat Theme (#3936)" This reverts commit 98b9f7d. * Revert Inline Image GA changes * Fix lint issues * Change files * Duplicate change files for beta release * Separate file sharing with inline image * Remove test CC * Update FileDownloadCards.test.tsx * Update ChatScreen.tsx * Merge strings back into main (#4025) * TDBuild - updating localized resource files. * Improve CI workflow (#4016) * Lock Files * Change files * Duplicate change files for beta release * Update lock files * Skip compare jest coverage and compare bundle size CI steps for PRs to release (#4026) * Skip jest test coverage and compare bundle stats steps when base branch is a release branch * Change files * Duplicate change files for beta release * [OCE] Remove beta banner for features that are stable (#4031) * remove sounds beta banner * Change files * Duplicate change files for beta release * [Calling] Applying capability for Reaction feature (#4013) * Fix calling sample joining room with room id query arg (#4032) * Fix calling sample to be able to join room with roomId query arg * Change files * Duplicate change files for beta release * Update packages/react-composites ChatComposite browser test snapshots * Update packages/react-composites ChatComposite browser test snapshots --------- Signed-off-by: Donald McEachern <94866715+dmceachernmsft@users.noreply.github.com> Signed-off-by: Patrick Latter <73612854+palatter@users.noreply.github.com> Co-authored-by: Donald McEachern <94866715+dmceachernmsft@users.noreply.github.com> Co-authored-by: Emlyn Bolton <3941071+emlynmac@users.noreply.github.com> Co-authored-by: James Burnside <2684369+JamesBurnside@users.noreply.github.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Mohtasim <99507832+Mohtasim@users.noreply.github.com> Co-authored-by: mgamis-msft <79475487+mgamis-msft@users.noreply.github.com> Co-authored-by: carocao-msft <96077406+carocao-msft@users.noreply.github.com> Co-authored-by: vhuseinova-msft <98852890+vhuseinova-msft@users.noreply.github.com> Co-authored-by: Leah Xia <107075081+Leah-Xia-Microsoft@users.noreply.github.com> Co-authored-by: edwardlee-msft <edwardlee@microsoft.com>
What
Break out jest coverage to a separate parallel job.
Remove hard coding of node version and global rush version
Why
Improve maintainability
How Tested
CI
Process & policy checklist
Is this a breaking change?