@bigbinary/neeto-team-members-frontend 2.10.6 → 2.10.8

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -2,22 +2,27 @@
2
2
 
3
3
  The `neeto-team-members-nano` facilitates the administration of team members within neeto applications. The nano exports the `@bigbinary/neeto-team-members-frontend` NPM package and `neeto-team-members-engine` Rails engine for development.
4
4
 
5
- # Contents
5
+ ## Contents
6
+
6
7
  1. [Development with Host Application](#development-with-host-application)
7
8
  - [Engine](#engine)
8
- * [Installation](#installation)
9
- * [Usage](#usage)
9
+ - [Installation](#installation)
10
+ - [Usage](#usage)
10
11
  - [Frontend package](#frontend-package)
11
- * [Installation](#installation-1)
12
- * [Components](#components)
12
+ - [Installation](#installation-1)
13
+ - [Components](#components)
13
14
  2. [Instructions for Publishing](#instructions-for-publishing)
14
15
 
15
- # Development with Host Application
16
- ## Engine
16
+ ## Development with Host Application
17
+
18
+ ### Engine
19
+
17
20
  The engine is used to seed the roles and permissions for the organization. It also provides concerns to handle common logic related to `User` model.
18
21
 
19
- ### Installation
22
+ #### Installation
23
+
20
24
  1. Add this line to your application's Gemfile:
25
+
21
26
  ```ruby
22
27
  source "NEETO_GEM_SERVER_URL" do
23
28
  # ..existing gems
@@ -25,51 +30,75 @@ The engine is used to seed the roles and permissions for the organization. It al
25
30
  gem 'neeto-team-members-engine'
26
31
  end
27
32
  ```
33
+
28
34
  2. And then execute:
35
+
29
36
  ```shell
30
37
  bundle install
31
38
  ```
39
+
32
40
  3. Add this line to your application's `config/routes.rb` file:
41
+
33
42
  ```ruby
34
43
  mount NeetoTeamMembersEngine::Engine => "/neeto_team_members_engine"
35
44
  ```
45
+
36
46
  4. Run the command to bring in all migrations required from the engine to the host application:
47
+
37
48
  ```shell
38
49
  bundle exec rails neeto_team_members_engine:install:migrations
39
50
  ```
51
+
40
52
  5. Add the migrations to the database:
53
+
41
54
  ```shell
42
55
  bundle exec rails db:migrate
43
56
  ```
57
+
44
58
  6. Now, run the generator which will copy the required files.
59
+
45
60
  ```shell
46
61
  bundle exec rails g neeto_team_members_engine:install
47
62
  ```
63
+
48
64
  This command will try to inject the engine's route as well as create a `config/permissions.yml` file to add the permissions required.
49
65
 
50
- ### Usage
66
+ #### Usage
67
+
51
68
  You can learn more about the setup and usage here:
69
+
52
70
  1. [Permissions](./docs/engine/permissions.md)
53
71
  2. [Roles](./docs/engine/roles.md)
54
72
  3. [Concerns](./docs/engine/concerns.md)
55
73
 
56
- ## Frontend package
74
+ ### Frontend package
75
+
57
76
  The package exports the four components: `Roles`, `TeamMembers`, `Permissions`, and `ManageRole`.
58
77
 
59
- ### Installation
60
- Install the latest `NeetoTeamMembersnano` package using the below command:
78
+ #### Installation
79
+
80
+ Install the latest `NeetoTeamMembersNano` package using the below command:
61
81
 
62
82
  ```shell
63
83
  yarn add @bigbinary/neeto-team-members-frontend
64
84
  ```
65
- ### Components
66
- #### `Roles`
85
+
86
+ #### Components
87
+
88
+ ##### `Roles`
89
+
67
90
  This component manages team roles. It includes functionalities such as adding roles and allowing updates to roles with associated permissions.
68
- ##### Props
91
+
92
+ ###### Props
93
+
69
94
  - `config`: Configuration object that includes mandatory specifications for header breadcrumbs and role permissions. It also allows optional configurations for help articles and permission hierarchy.
70
- ##### Configuration
95
+
96
+ ###### Configuration
97
+
71
98
  Refer to the [Roles](./docs/frontend/roles.md) section for detailed information on the available configurations for the `Roles` component.
72
- ##### Usage
99
+
100
+ ###### Usage
101
+
73
102
  ```jsx
74
103
  import React from "react";
75
104
 
@@ -95,13 +124,21 @@ const App = () => (
95
124
 
96
125
  export default App;
97
126
  ```
98
- #### `TeamMembers`
127
+
128
+ ##### `TeamMembers`
129
+
99
130
  The component offers functionalities for adding, updating and viewing team members and their roles in a tabular format. Additionally, it provides filtering options based on email, name, and role.
100
- ##### Props
131
+
132
+ ###### Props
133
+
101
134
  - `config`: Configuration object that allows customization of role management, member operation permissions, UI elements like buttons and headers, callback functions, table structure, dropdown actions, and various display aspects.
102
- ##### Configuration
135
+
136
+ ###### Configuration
137
+
103
138
  Refer to the [TeamMembers](./docs/frontend/team_members.md) section for detailed information on the available configurations for the `TeamMembers` component.
104
- ##### Usage
139
+
140
+ ###### Usage
141
+
105
142
  ```jsx
106
143
  import React from "react";
107
144
 
@@ -128,15 +165,22 @@ const App = () => (
128
165
  export default App;
129
166
  ```
130
167
 
131
- #### `Permissions`
168
+ ##### `Permissions`
169
+
132
170
  The component handles the rendering and management of permissions for team members. It organizes permissions into categories, provides checkboxes for selection, and supports hierarchical structures with parent-child relationships.
133
- ##### Props
171
+
172
+ ###### Props
173
+
134
174
  - `permissions`: An array of permissions.
135
175
  - `isDisabled`: A boolean indicating whether the component is disabled. By default, it is false.
136
176
  - `permissionRelationConfig`: Configuration for managing parent-child relationships and unchecking permissions on select.
137
- ##### Configuration
177
+
178
+ ###### Configuration
179
+
138
180
  Refer to the [Permissions](./docs/frontend/permissions.md) section for detailed information on the available configurations for the `TeamMembers` component.
139
- ##### Usage
181
+
182
+ ###### Usage
183
+
140
184
  ```jsx
141
185
  import React from "react";
142
186
 
@@ -166,18 +210,24 @@ const App = () => (
166
210
  export default App;
167
211
  ```
168
212
 
169
- #### `ManageMembers`
213
+ ##### `ManageMembers`
214
+
170
215
  The component is a form-based interface for adding or editing team members.
171
- ##### Props
216
+
217
+ ###### Props
218
+
172
219
  - `config`: Configuration object with various options for customizing the behavior of the component.
173
220
  - `onComplete`: Callback function to be executed when the component is closed or the form is submitted.
174
221
  - `roles`: An array of roles available for team members.
175
222
  - `selectedMember`: The team member object being edited, if applicable.
176
223
  - `componentConfig`: Configuration specific to the component, including the type of pane, initial focus reference, etc.
177
224
 
178
- ##### Configuration
225
+ ###### Configuration
226
+
179
227
  Refer to the [ManageMembers](./docs/frontend/manage_members.md) section for detailed information on the available configurations for the `ManageMembers` component.
180
- ##### Usage
228
+
229
+ ###### Usage
230
+
181
231
  ```jsx
182
232
  import React from "react";
183
233
 
@@ -207,6 +257,40 @@ const App = () => (
207
257
 
208
258
  export default App;
209
259
  ```
210
- # Instructions for Publishing
260
+
261
+ ## Instructions for Publishing
211
262
 
212
263
  Consult the [building and releasing packages](https://neeto-engineering.neetokb.com/articles/building-and-releasing-packages) guide for details on how to publish.
264
+
265
+ ## Integrations
266
+
267
+ | Projects | TeamMembers | Roles | Permissions |
268
+ |----------------| :----------------: | :----------------: | :----------------: |
269
+ | neetoAuth | :white_check_mark: | :white_check_mark: | - |
270
+ | neetoCal | :white_check_mark: | :white_check_mark: | - |
271
+ | neetoChangelog | :white_check_mark: | :white_check_mark: | - |
272
+ | neetoChat | :white_check_mark: | :white_check_mark: | - |
273
+ | neetoChatify | :white_check_mark: | :white_check_mark: | - |
274
+ | neetoCI | :white_check_mark: | :white_check_mark: | - |
275
+ | neetoCourse | :white_check_mark: | :white_check_mark: | - |
276
+ | neetoCRM | :white_check_mark: | :white_check_mark: | - |
277
+ | neetoDeploy | :white_check_mark: | :white_check_mark: | :white_check_mark: |
278
+ | neetoDesk | :white_check_mark: | :white_check_mark: | - |
279
+ | neetoForm | :white_check_mark: | :white_check_mark: | - |
280
+ | neetoGit | :white_check_mark: | :white_check_mark: | - |
281
+ | neetoInvisible | :white_check_mark: | :white_check_mark: | - |
282
+ | neetoInvoice | :white_check_mark: | :white_check_mark: | - |
283
+ | neetoKB | :white_check_mark: | :white_check_mark: | - |
284
+ | neetoMonitor | :white_check_mark: | :white_check_mark: | - |
285
+ | neetoPlanner | :white_check_mark: | :white_check_mark: | - |
286
+ | neetoQuiz | :white_check_mark: | :white_check_mark: | - |
287
+ | neetoRecord | :white_check_mark: | :white_check_mark: | - |
288
+ | neetoReplay | :white_check_mark: | :white_check_mark: | - |
289
+ | neetoRunner | :white_check_mark: | :white_check_mark: | - |
290
+ | neetoSign | :white_check_mark: | :white_check_mark: | - |
291
+ | neetoSite | :white_check_mark: | :white_check_mark: | - |
292
+ | neetoTestify | :white_check_mark: | :white_check_mark: | - |
293
+ | neetoTower | :white_check_mark: | :white_check_mark: | - |
294
+ | neetoTrail | :white_check_mark: | :white_check_mark: | - |
295
+ | neetoWheel | :white_check_mark: | :white_check_mark: | - |
296
+ | neetoWireframe | :white_check_mark: | :white_check_mark: | - |