OpenUI5 Documentation Update 31.01.2024

Author: openui5bot

docs/Annotation_Helper_dbec058.md

@@ -30,22 +30,6 @@ The formatter functions can be used in binding expressions and `<template:if>` i
 
 The following formatter functions exist:
 
--   `createPropertySetting`: Creates a property setting which is either a constant value or a binding info object from the given parts and from the optional root formatter function. Each part can have one of the following types:
-
-    -   boolean, number, undefined: The part is a constant value.
-
-    -   string: The part is a data binding expression with complex binding syntax \(for example, as created by format\) and is parsed accordingly to create either a constant value or a binding info object. Proper backslash escaping must be used for constant values with curly braces.
-
-    -   object: The part is a binding info object if it has a "path" or "parts" property, otherwise it is a constant value.
-
-
-    If a binding info object is not the only part and has a `parts` property itself, then it must have no other properties except `formatter`. This applies to expression bindings and data binding expressions that are created by `format`. If all parts are constant values, the resulting property setting is also a constant value computed by applying the root formatter function to the constant parts once. If at least one part is a binding info object, the resulting property setting is also a binding info object and the root formatter function will be applied again and again to the current values of all parts, no matter whether constant or variable.
-
-    > ### Note:  
-    > The root formatter function should not rely on its `this` value because it depends on how the function is called.
-    > 
-    > A single data binding expression can be given directly to `applySettings`; you do **not** need to call `this` function first.
-
 -   `format`: General purpose method that handles proper escaping and formatting of constant values and provides binding expressions with suitable types. `format` supports the following constructs:
 
     -   The *"14.4 Constant Expressions"* for *"edm:Bool"*, *"edm:Date"*, *"edm:DateTimeOffset"*, *"edm:Decimal"*, *"edm:Float"*, *"edm:Guid"*, *"edm:Int"*, *"edm:TimeOfDay"*.

docs/Cookbook_for_Testing_Controls_with_QUnit_0ddcc60.md

@@ -176,7 +176,7 @@ QUnit.test("Test with fake timers", async() => {
 
     // Release all timers at the end of the test
     // to avoid e.g. blocking the rendering within
-    // following tests and to ensure, that other
+    // following tests and to ensure that other
     // timeouts triggered through integration are
     // released
     oButton.destroy()
@@ -226,37 +226,6 @@ QUnit.test("Should suppress rerendering when tooltip is set", async(assert) => {
 });
 ```
 
-`applyChanges()` enforces a synchronous rendering and **must not** be used in productive code.
-
-**For test scenarios only**, you may use the test helper module **`sap/ui/qunit/utils/nextUIUpdate`** instead.
-
-> ### Restriction:  
-> Using `nextUIUpdate` in combination with fake timers has some pitfalls. If fake timers are used, it is not possible to use `await`. In this case, you need to chain to the `nextUIUpdate` Promise and always use `clock.tick()` within the chaining in order to execute the rendering.
-> 
-> The main difference to `applyChanges()` is that `nextUIUpdate()` does not synchronously trigger a re-rendering \(which by intention we wanted to get rid of\), but just waits for the next rendering cycle to complete. Due to this asynchronous nature, switching to it may be slightly more work than in other more straightforward cases.
-
-As a replacement for `applyChanges()` **in tests only**, use:
-
-```js
-QUnit.test("Simple Component Instance",
-  async function(assert){
-    await nextUIUpdate();
-    ...
-});
- 
-// nextUIUpdate with fake timers
-QUnit.test("Test with fake timers", function() {
-    this.clock = sinon.useFakeTimers();
- 
-    // Using runAll is not always necessary but ensures, that no timeouts are left unprocessed
-    this.clock.runAll();
-    nextUIUpdate().then(() => {
-        this.clock.tick();
-        // Continue with your test
-    });
-}
-```
-
 ***
 
 ### Testing with Models
@@ -349,7 +318,7 @@ QUnit.test("Should do something with the model", async(assert) => {
         oMockServer = startMockServer(50);
 
     // System under Test
-    constoLabel = new Label({
+    const oLabel = new Label({
         text : "{/myProperty}"
     });
 

docs/How_to_Test_OpenUI5_Controls_with_QUnit_a6b0657.md

@@ -142,10 +142,6 @@ Using fake timers can be error-prone. Fake timers should only be used with care
 
 -   For using fake timers in combination with rendering: [Rendering and Re-rendering Controls Within Tests](Cookbook_for_Testing_Controls_with_QUnit_0ddcc60.md#loio0ddcc60b05ee40dea1a3be09e8fee8f7__section_REREN)
 
-If you are using `sinon.qunit`, it will automatically use fake timers by itself. Fake timers will prevent any `setTimeout/setIntervall` function from being executed, unless you call `this.clock.tick(milliseconds)` in your test. This means that a Mock Server with auto-respond will not respond and OPA will not be able to wait for controls.
-
-In addition, control events might be fired inside of a `setTimeout(, 0)`, so the event might not be triggered at all.
-
 ***
 
 #### I've set a property on my control: Why aren't the changes in the DOM?

docs/Legacy_Factories_Replacement_491bd9c.md

@@ -294,7 +294,7 @@ var oView = sap.ui.jsview({
 </td>
 <td valign="top">
 
-For defining views, use `View.extend`. For loading and creating a view instance, use `View.create`. Refer also to the dedicated [Typed View](Typed_View_e6bb33d.md) documentation and the[code sample](https://sdk.openui5.org/entity/sap.ui.core.mvc.View/sample/sap.ui.core.sample.View.navigationTypedView).
+For defining views, use `View.extend`. For loading and creating a view instance, use `View.create`. Refer also to the dedicated [Typed View](Typed_View_e6bb33d.md) documentation and the [code sample](https://sdk.openui5.org/entity/sap.ui.core.mvc.View/sample/sap.ui.core.sample.View.navigationTypedView).
 
 ```
 
@@ -449,7 +449,7 @@ var aControls = sap.ui.jsfragment({
 
 ```
 // XML Fragments
-var aControls = sap.ui.fragment({ 
+var aControls = sap.ui.xmlfragment({ 
     name: "my.fragment"
 });