Skip to content
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

FUSETOOLS2-2065: Provide tests for completion inside tasks.json #529

Merged
merged 1 commit into from
Nov 10, 2023

Conversation

pospisilf
Copy link
Contributor

@pospisilf pospisilf commented Nov 6, 2023

Compiler changed to ES2022 to add support for .at() function on String[] to allow test parameterization.  

src/ui-test/tests/tasks.json.autocompletion.test.ts Outdated Show resolved Hide resolved
tsconfig.json Outdated Show resolved Hide resolved
src/ui-test/variables.ts Outdated Show resolved Hide resolved
tsconfig.json Outdated
],
"sourceMap": true,
"rootDir": "src",
"skipLibCheck": true,
"strict": true /* enable all strict type-checking options */
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what is the reason to remove the turn strict to false?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good point, I have forgot to mention that and discuss further the best approach..

it is mainly because we wanted to reuse same functions as in LSP without changing them, problem is that LSP project is not using strict and same tsconfig setup as DAP extension which causes problems.. so we were considering in the first iteration to reuse same functions to stay consistent for utils we are using across projects and in the next iteration we wanted to unify tsconfigs for both projects and fix utils functions which could be done in another issue/PR (already opened and selected for dev https://issues.redhat.com/browse/FUSETOOLS2-2256)

so we wrere considering options like what is better..

  1. for this PR revert strict change, copy functions and modify them to be compliant but in that case different from LSP ones
  2. remove strict for some time then fusetools2-2256 will be resolved and reuse same functions for now

in the end probably better to let strict there as is and revise everything for both projects in another mentioned issue 🤷‍♂️.. I can see Filip already reverted tsconfig change of strict option

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

basically problem is that we need to

  1. unify tsconfigs across our extensions projects
  2. finally provide just one shared test utils we can share across projects to prevent these copy&paste and hard maintain issues..

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

both solution seems reasonable

Copy link

sonarqubecloud bot commented Nov 9, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@pospisilf pospisilf requested a review from djelinek November 9, 2023 13:51
@pospisilf pospisilf merged commit dcdd7be into camel-tooling:main Nov 10, 2023
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants