We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
There seem to be some changes to the ui5 bootstrap parameters so the preview sandbox template needs to be adjusted.
data-sap-ui-compatVersion
data-sap-ui-compat-version
data-sap-ui-resourceroots
data-sap-ui-resource-roots
data-sap-ui-oninit
sample from other project:
Not sure about the downward compatibility. But outdated notation might not be available in UI5 2.x
Steps to reproduce the behavior:
No ui5Linter issues
ui5Linter issues
Add any other context about the problem here OS:
{describe the problem}
{describe the fix}
{Some explanation why this issue might have been missed during normal development/testing cycle}
{if we don’t want to see this type of issues anymore what we should do to prevent}
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Description
There seem to be some changes to the ui5 bootstrap parameters so the preview sandbox template needs to be adjusted.
data-sap-ui-compatVersion
->data-sap-ui-compat-version
data-sap-ui-resourceroots
->data-sap-ui-resource-roots
data-sap-ui-oninit
->data-sap-ui-oninit
sample from other project:
Not sure about the downward compatibility. But outdated notation might not be available in UI5 2.x
Steps to Reproduce
Steps to reproduce the behavior:
Expected results
No ui5Linter issues
Actual results
ui5Linter issues
Version/Components/Environment
Add any other context about the problem here
OS:
Root Cause Analysis
Problem
{describe the problem}
Fix
{describe the fix}
Why was it missed
{Some explanation why this issue might have been missed during normal development/testing cycle}
How can we avoid this
{if we don’t want to see this type of issues anymore what we should do to prevent}
The text was updated successfully, but these errors were encountered: