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

[MPQEditor] Update MPQData for visq path. #1547

Merged
merged 1 commit into from
May 2, 2023

Conversation

stamalakhov
Copy link
Contributor

This commit updates MPQData for handling visq path.

Its correctness is tested in #1543

Fresh draft: #1543
Full draft: #1505
Related: #1491

ONE-vscode-DCO-1.0-Signed-off-by: s.malakhov s.malakhov@partner.samsung.com

@stamalakhov stamalakhov self-assigned this Apr 28, 2023
@stamalakhov stamalakhov requested review from dayo09 and removed request for jinevening April 28, 2023 15:41
@@ -139,6 +140,14 @@ export class MPQData {
return layersToAdd;
}

getVisqPath(): string {
Copy link
Contributor

@dayo09 dayo09 May 2, 2023

Choose a reason for hiding this comment

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

(optional) FYI, typescript provides 'get' 'set' keywords for easier getter/setter implementation. 😄

Copy link
Contributor Author

Choose a reason for hiding this comment

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

(optional) FYI, typescript provides 'get' 'set' keywords for easier getter/setter implementation. 😄

@dayo09
Thank you! I've changed the draft and this PR.

This draft introduces VISQ data.

ONE-vscode-DCO-1.0-Signed-off-by: s.malakhov <s.malakhov@partner.samsung.com>
Copy link
Contributor

@seanshpark seanshpark left a comment

Choose a reason for hiding this comment

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

LGTM

@seanshpark seanshpark merged commit 67f44f3 into Samsung:main May 2, 2023
6 checks passed
@stamalakhov stamalakhov deleted the manual_MPQ_visq_data_br branch May 2, 2023 06:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants