New Features in MDK extension for VS Code 1.2
I am happy to announce that a new release of the Mobile Development Kit (MDK) extension for Visual Studio (VS) Code is available for download on the SAP Marketplace and the Visual Studio Marketplace. You can also view the changelog on Visual Studio Marketplace.
Mobile development kit (MDK) is a feature of SAP Cloud Platform Mobile Services. If this is your first introduction to the mobile development kit, I suggest you first review the Learning Map which provides overview topics, blogs, videos, and tutorials.
Here is a list of the new features in 1.2.
- Support for debugging on Android emulator
- Support for internationalization and localization
- Support for reusable components
- Indicators for platform specific metadata
Support for debugging on Android emulator
As you may have read in this blog, MDK has expanded support to include Android. So, the MDK extension for VS Code now supports Android for debugging MDK applications as well. In order to debug on an Android emulator, you will first need to install the MDK 3.0 SDK client and enable for Android. You can review the blog mentioned earlier to sign up for the MDK 3.0 Early Adopter Care program to get the MDK 3.0 SDK.
Once you do that, you can add a new launch config for Android debugging in the extension. Follow the instructions in the MDK help portal for more information on creating launch configurations.
Support for internationalization and localization
The MDK extension now includes language features while editing the MDK application. Features include:
When entering string values in a MDK field, use $ to display all the localization keys from the localization file specified in the Application.app. For an i18n indicator, input comma (,) to trigger the suggestion list for the next parameter to be provided.
The MDK extension validates that a localization key specified in a field actually exists in the localization file. If the localization key does not exist, you will receive an error message and details will be shown in the PROBLEMS panel.
Go to definition
Put the cursor within a valid localization key in the MDK page you are editing, then select the “Go to Definition” context menu item. The corresponding localization property file will be opened to the beginning of the localization key you navigated from.
Support for reusable components
The MDK extension now includes support for reusable components. If you are unfamiliar with reusable components, review this blog.
From within Visual Studio Code, you can
- Create cim file via the context menu of app and choose another MDK application within the existing workspace to do the component integration.
- Within the cim file, you specify the integration points which include a source and target.
- Bundling will include both base application and the referenced component applications.
- Debugging the overriding rule files via cross application breakpoints take place in the base application and linked component applications.
Indicators for platform specific metadata
While MDK tries to consolidate the metadata for Android and iOS, some properties may be platform specific. The MDK editor for VS Code helps you identify these platform specific properties.
If a value is platform-specific, a note about the platform where the value is used will be displayed side by side with the completion list when it is chosen.
If a value is platform-specific, e.g. the value “FixedSpace” of SystemItem for ActionBar, a warning will be displayed in the two following places:
- In the PROBLEMS view, the following warning message type will be displayed, e.g. “The value <property> is only used on the iOS platform”.
- In the editor, when you hover over the green tilde, a tool tip will be displayed above the warning message.
How I debug an overriding rule?. I am creating a breakpoint in the extension rule mapped through CIM file and it doesnt stop. If a put a breakpoint in the base rule it stop. So, how I can debug it?
Is this functionality available and working?
Thanks in advance,