Skip to content

fix: Valid Js syntax after XML transpilation#552

Merged
d3xter666 merged 2 commits intomainfrom
fix-xml-transpier-exports
Feb 21, 2025
Merged

fix: Valid Js syntax after XML transpilation#552
d3xter666 merged 2 commits intomainfrom
fix-xml-transpier-exports

Conversation

@d3xter666
Copy link
Member

Resolves an issue where the tranpiled XML->Js is exported with a syntax error.
Now this is fixed and the export statements are valid.

Currently, this is not an issue for the linter, but in future this might lead to unexpected results if we try to analyze exports.

@d3xter666 d3xter666 requested review from a team, codeworrior and matz3 February 19, 2025 15:21
});␊
export default const oView = new View({␊
const oView = new View({␊
Copy link
Member

Choose a reason for hiding this comment

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

why not export new View({?

Copy link
Member Author

Choose a reason for hiding this comment

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

Basically, this is the simplest solution that will not break anything.
The impact of this change is just the export of XMLView.
However, if we want to implement export default new View..., then we'll need to also modify the code for variable declaration & initialization which resides in another module and will definitelly imact the other scenarios

@d3xter666 d3xter666 merged commit 98b89d5 into main Feb 21, 2025
16 checks passed
@d3xter666 d3xter666 deleted the fix-xml-transpier-exports branch February 21, 2025 12:05
@openui5bot openui5bot mentioned this pull request Feb 20, 2025
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.

3 participants