@iobroker/gui-components 10.4.1 → 10.4.2

package/README.md

@@ -36,7 +36,7 @@ npm create vite@latest src -- --template react-ts
     "dependencies": {
         "@emotion/react": "^11.14.0",
         "@emotion/styled": "^11.14.1",
-        "@iobroker/gui-components": "^10.4.1",
+        "@iobroker/gui-components": "^10.4.2",
         "@mui/icons-material": "^9.0.1",
         "@mui/material": "^9.0.1",
         "react": "^19.2.5",
@@ -877,6 +877,10 @@ You can find the migration instructions:
 -->
 
 ## Changelog
+### 10.4.2 (2026-11-05)
+- (@GermanBluefox) Added: `ObjectBrowser` prop `objectsNotEditable`: objects read-only, state values still editable
+- (@GermanBluefox) Added: `ObjectBrowser` checks the rights of each object: no edit or delete where the user may not
+
 ### 10.4.1 (2026-11-05)
 - (@GermanBluefox) Changed: `UploadImage`: the upload symbol is animated (it bobs while a file is dragged over the drop area and moves up while the file is read), the drop area pulses while a file is dragged over it, also over an existing image, and a new image fades in
 - (@GermanBluefox) Added: `UploadImage` got the props `uploading` and `uploadError`: while the parent uploads the image (e.g. writes it into a file) an upload arrow is shown in the corner of the image, followed by a check mark or a cross

package/build/Components/ObjectBrowser/ObjectBrowserClass.d.ts

@@ -248,6 +248,17 @@ export declare class ObjectBrowserClass extends Component<ObjectBrowserProps, Ob
      * @param id ID of the object
      */
     isDeleteAllowed(id: string): boolean;
+    /**
+     * May the user change this object (`object`) or the value of this state (`state`)? Asks the
+     * connection, which knows the rights of the group of the user and checks the rights of the object
+     * itself (`obj.acl`) as js-controller does. Without known rights - or with a connection that
+     * cannot tell - the answer is yes and the server decides.
+     *
+     * @param obj the object
+     * @param part `object` for the object itself, `state` for the value of a state
+     * @param operation `delete` to delete the object
+     */
+    mayChange(obj: ioBroker.Object | null | undefined, part?: 'object' | 'state', operation?: 'write' | 'delete'): boolean;
     /**
      * Show the deletion dialog for a given object
      */

package/build/Components/ObjectBrowser/ObjectBrowserClass.js

@@ -845,6 +845,22 @@ export class ObjectBrowserClass extends Component {
     isDeleteAllowed(id) {
         return this.state.filter.expertMode || USER_OWNED_NAMESPACES.some(prefix => id.startsWith(prefix));
     }
+    /**
+     * May the user change this object (`object`) or the value of this state (`state`)? Asks the
+     * connection, which knows the rights of the group of the user and checks the rights of the object
+     * itself (`obj.acl`) as js-controller does. Without known rights - or with a connection that
+     * cannot tell - the answer is yes and the server decides.
+     *
+     * @param obj the object
+     * @param part `object` for the object itself, `state` for the value of a state
+     * @param operation `delete` to delete the object
+     */
+    mayChange(obj, part = 'object', operation = 'write') {
+        // `hasObjectPermission` came with @iobroker/socket-client 5.6.0. Described here, so that this
+        // compiles and runs with an older socket client as well - which does not know the method
+        const socket = this.props.socket;
+        return typeof socket?.hasObjectPermission !== 'function' || socket.hasObjectPermission(obj, operation, part);
+    }
     /**
      * Show the deletion dialog for a given object
      */