Fix "copyValueTo" feature in layout settings

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,59 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Describe the bug**
+which template:
+
+* [ ] MaterialDesignFrameworkModule — Material Design
+* [ ] Bootstrap3FrameworkModule — Bootstrap 3
+* [ ] Bootstrap4FrameworkModule — Bootstrap 4
+* [ ] Bootstrap5FrameworkModule — Bootstrap 5
+* [ ] DaisyUIFrameworkModule — DaisyUI
+* [ ] NoFrameworkModule — plain HTML
+* [ ] Other (please specify below)
+
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+
+1. ...
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Desktop (please complete the following information):**
+
+- OS: [e.g. iOS]
+- Browser [e.g. chrome, safari]
+- Version [e.g. 22]
+
+**Log output covering before error and any error statements**
+
+```logs
+Insert log hereCopy
+```
+
+**Additional context**
+Add any other context about the problem here.
+
+
+<!--- For feature requests -->
+**Detailed Description**
+<!--- Provide a detailed description of the change or addition you are proposing -->
+
+**Context**
+<!--- Why is this change important to you? How would you use it? -->
+<!--- How can it benefit other users? -->
+
+**Possible Implementation**
+<!--- Not obligatory, but suggest an idea for implementing addition or change -->

.github/workflows/createdist.yml

@@ -0,0 +1,113 @@
+#workflow creates a dist branch for each library, based on its package version
+#should create the following 2 dist branches per lib project
+#for example the material library project with package version x.x.x will create branches: 
+#dist_material
+#dist_material_vx.x.x
+
+name: CreateDist
+
+on:
+  push:
+    branches: [ main ]
+
+jobs:
+  deploy:
+    runs-on: ubuntu-latest
+
+    steps:
+    - uses: actions/checkout@v3
+
+    - name: setup Node
+      uses: actions/setup-node@v3
+    - run: npm ci
+    - run: npm run build:libs
+
+    - name: version core
+      uses: nyaa8/package-version@v1
+      with:
+       path: './dist/@zajsf/core/package.json'  
+
+    - name: dist core versioned
+      uses: s0/git-publish-subdir-action@develop
+      env:
+        REPO: self
+        BRANCH: dist_core_v${{ env.PACKAGE_VERSION }}
+        FOLDER: ./dist/@zajsf/core
+        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+
+    - name: dist core
+      uses: s0/git-publish-subdir-action@develop
+      env:
+        REPO: self
+        BRANCH: dist_core
+        FOLDER: ./dist/@zajsf/core
+        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}        
+
+    - name: version bootstrap3
+      uses: nyaa8/package-version@v1
+      with:
+       path: './dist/@zajsf/bootstrap3/package.json'    
+
+    - name: dist bootstrap3 versioned
+      uses: s0/git-publish-subdir-action@develop
+      env:
+        REPO: self
+        BRANCH: dist_bootstrap3_v${{ env.PACKAGE_VERSION }}
+        FOLDER: ./dist/@zajsf/bootstrap3
+        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+
+    - name: dist bootstrap3
+      uses: s0/git-publish-subdir-action@develop
+      env:
+        REPO: self
+        BRANCH: dist_bootstrap3
+        FOLDER: ./dist/@zajsf/bootstrap3
+        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}   
+
+    - name: version bootstrap4
+      uses: nyaa8/package-version@v1
+      with:
+       path: './dist/@zajsf/bootstrap4/package.json'          
+
+
+    - name: dist_bootstrap4 versioned
+      uses: s0/git-publish-subdir-action@develop
+      env:
+        REPO: self
+        BRANCH: dist_bootstrap4_v${{ env.PACKAGE_VERSION }}
+        FOLDER: ./dist/@zajsf/bootstrap4
+        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+
+    - name: dist_bootstrap4
+      uses: s0/git-publish-subdir-action@develop
+      env:
+        REPO: self
+        BRANCH: dist_bootstrap4
+        FOLDER: ./dist/@zajsf/bootstrap4
+        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}        
+
+
+    - name: version material
+      uses: nyaa8/package-version@v1
+      with:
+       path: './dist/@zajsf/material/package.json'  
+
+    - name: dist material versioned
+      uses: s0/git-publish-subdir-action@develop
+      env:
+        REPO: self
+        BRANCH: dist_material_v${{ env.PACKAGE_VERSION }}
+        FOLDER: ./dist/@zajsf/material
+        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+
+    - name: dist material
+      uses: s0/git-publish-subdir-action@develop
+      env:
+        REPO: self
+        BRANCH: dist_material
+        FOLDER: ./dist/@zajsf/material
+        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+
+
+
+

.github/workflows/dependabot.yml

@@ -13,31 +13,31 @@ updates:
       # Prefix all commit messages with "build"
       prefix: "build"
   - package-ecosystem: "npm"
-    directory: "/projects/ajsf-core"
+    directory: "/projects/zajsf-core"
     schedule:
       interval: "weekly"
       day: "sunday"
     open-pull-requests-limit: 5
     commit-message:
       prefix: "build"
   - package-ecosystem: "npm"
-    directory: "/projects/ajsf-material"
+    directory: "/projects/zajsf-material"
     schedule:
       interval: "weekly"
       day: "sunday"
     open-pull-requests-limit: 5
     commit-message:
       prefix: "build"
   - package-ecosystem: "npm"
-    directory: "/projects/ajsf-bootstrap3"
+    directory: "/projects/zajsf-bootstrap3"
     schedule:
       interval: "weekly"
       day: "sunday"
     open-pull-requests-limit: 5
     commit-message:
       prefix: "build"
   - package-ecosystem: "npm"
-    directory: "/projects/ajsf-bootstrap4"
+    directory: "/projects/zajsf-bootstrap4"
     schedule:
       interval: "weekly"
       day: "sunday"

.github/workflows/deploy-branch.yml

@@ -0,0 +1,28 @@
+name: DeployBranch
+
+on:
+  workflow_dispatch:
+    inputs:
+      branch:
+        description: 'Define branch name'     
+        required: true
+        default: 'main'
+
+jobs:
+  deploy:
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/checkout@v3
+      with:
+        ref: ${{ github.event.inputs.branch }}
+    - name: setup Node
+      uses: actions/setup-node@v3
+    - run: npm ci
+    - run: npm run build:demo
+
+    - name: deploy
+      uses: peaceiris/actions-gh-pages@v3
+      with:
+        github_token: ${{ secrets.GITHUB_TOKEN }}
+        publish_dir: ./dist/demo
+        exclude_assets: ''

CONTRIBUTING.md

@@ -1,15 +1,15 @@
-# Contributing to ajsf
+# Contributing to zajsf
 
-ajsf is an open project and welcomes contributions. These guidelines are provided to help you understand how the project works and to make contributing smooth and fun for everybody involved.
+zajsf is an open project and welcomes contributions. These guidelines are provided to help you understand how the project works and to make contributing smooth and fun for everybody involved.
 
 There are two main forms of contribution: reporting issues and performing code changes.
 
 ## Reporting Issues
 
-If you find a problem with ajsf, report it using [GitHub issues](https://github.com/hamzahamidi/ajsf/issues/new).
+If you find a problem with zajsf, report it using [GitHub issues](https://github.com/zahmo/zajsf/issues/new).
 
 Before reporting a new issue, please take a moment to check whether it has already been reported
-[here](https://github.com/hamzahamidi/ajsf/issues). If this is the case, please:
+[here](https://github.com/zahmo/zajsf/issues). If this is the case, please:
 
 - Read all the comments to confirm that it's the same issue you're having.
 - Refrain from adding "same thing here" or "+1" comments. Just hit the
@@ -43,7 +43,7 @@ To send your code change, use GitHub pull requests. The workflow is as follows:
 
   1. Publish the branch and create a pull request.
 
-  1. ajsf developers will review your change and possibly point out issues.
+  1. zajsf developers will review your change and possibly point out issues.
      Adapt the code under their guidance until all issues are resolved.
 
   1. Finally, the pull request will get merged or rejected.
@@ -58,15 +58,15 @@ requests.
 Let's first generate all the bundles we need to start the demo:
 
 ```bash
-$ cd ajsf
+$ cd zajsf
 $ yarn install or npm install
 $ yarn start
 ```
 
 You can stop the demo application.
 The tricky part now is to run concurrently both the demo application & the library in watch mode.
-So, first choose which library you want to change then run `$ ng build @ajsf/core --watch` for example
-to build in watch mode the `@ajsf/core`.
+So, first choose which library you want to change then run `$ ng build @zajsf/core --watch` for example
+to build in watch mode the `@zajsf/core`.
 Now let's start the demo application in watch mode too. So, open a new terminal and run `$ ng serve` and there you go.
 This method is tricky but it works perfectly in all environments (I tried other methods like npm-run-all
 or concurrently packages but angular-cli build doesn't restart after a failed build).
@@ -128,10 +128,13 @@ The scope should be the name of the npm package affected (as perceived by the pe
 
 The following is the list of supported scopes:
 
-* **ajsf/core**
-* **ajsf/bs3**
-* **ajsf/bs4**
-* **ajsf/material**
+* **zajsf/core**
+* **zajsf/cssfw**
+* **zajsf/bs3**
+* **zajsf/bs4**
+* **zajsf/bs5**
+* **zajsf/daisyui**
+* **zajsf/material**
 * **locales**
 * **demo**
 * ...

LICENSE

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2018 Hamza Hamidi
+Copyright (c) 2014-2016 David Schnell-Davis 2018 Hamza Hamidi 2023 Zaheer M
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal