@longvansoftware/storefront-js-client 2.9.3 → 2.9.5

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
@@ -1,93 +1,186 @@
1
- # storefront-js-client
2
-
3
-
4
-
5
- ## Getting started
6
-
7
- To make it easy for you to get started with GitLab, here's a list of recommended next steps.
8
-
9
- Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
10
-
11
- ## Add your files
12
-
13
- - [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
14
- - [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
15
-
16
- ```
17
- cd existing_repo
18
- git remote add origin https://gitlab.longvan.vn/long-van-platform-2.0/website/storefront-js-client.git
19
- git branch -M main
20
- git push -uf origin main
21
- ```
22
-
23
- ## Integrate with your tools
24
-
25
- - [ ] [Set up project integrations](https://gitlab.longvan.vn/long-van-platform-2.0/website/storefront-js-client/-/settings/integrations)
26
-
27
- ## Collaborate with your team
28
-
29
- - [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
30
- - [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
31
- - [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
32
- - [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
33
- - [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
34
-
35
- ## Test and Deploy
36
-
37
- Use the built-in continuous integration in GitLab.
38
-
39
- - [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
40
- - [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
41
- - [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
42
- - [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
43
- - [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
44
-
45
- ***
46
-
47
- # Editing this README
48
-
49
- When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
50
-
51
- ## Suggestions for a good README
52
-
53
- Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
54
-
55
- ## Name
56
- Choose a self-explaining name for your project.
57
-
58
- ## Description
59
- Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
60
-
61
- ## Badges
62
- On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
63
-
64
- ## Visuals
65
- Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
66
-
67
- ## Installation
68
- Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
69
-
70
- ## Usage
71
- Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
72
-
73
- ## Support
74
- Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
75
-
76
- ## Roadmap
77
- If you have ideas for releases in the future, it is a good idea to list them in the README.
78
-
79
- ## Contributing
80
- State if you are open to contributions and what your requirements are for accepting them.
81
-
82
- For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
83
-
84
- You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
85
-
86
- ## Authors and acknowledgment
87
- Show your appreciation to those who have contributed to the project.
88
-
89
- ## License
90
- For open source projects, say how it is licensed.
91
-
92
- ## Project status
93
- If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
1
+ # Longvan Storefront JavaScript Client SDK
2
+
3
+ [![npm version](https://badge.fury.io/js/%40longvansoftware%2Fstorefront-js-client.svg)](https://badge.fury.io/js/%40longvansoftware%2Fstorefront-js-client)
4
+ [![TypeScript](https://img.shields.io/badge/%3C%2F%3E-TypeScript-%230074c1.svg)](http://www.typescriptlang.org/)
5
+ [![License: ISC](https://img.shields.io/badge/License-ISC-blue.svg)](https://opensource.org/licenses/ISC)
6
+
7
+ A comprehensive TypeScript/JavaScript SDK for integrating with the Longvan e-commerce platform. This SDK provides easy-to-use interfaces for managing products, orders, users, payments, and other e-commerce functionalities.
8
+
9
+ ## 🚀 Quick Start
10
+
11
+ ```bash
12
+ npm install @longvansoftware/storefront-js-client
13
+ ```
14
+
15
+ ```typescript
16
+ import { SDK } from '@longvansoftware/storefront-js-client';
17
+
18
+ const sdk = new SDK('your-org-id', 'your-store-id', 'dev');
19
+ sdk.setToken('your-access-token');
20
+
21
+ // Ready to use!
22
+ const products = await sdk.product.getSimpleProducts({ currentPage: 1, maxResult: 10 });
23
+ ```
24
+
25
+ ## 📚 Documentation
26
+
27
+ ### 🎯 Getting Started
28
+ - **[Installation & Setup](./docs/getting-started/installation.md)** - Complete installation guide
29
+ - **[Quick Start Guide](./docs/getting-started/quick-start.md)** - Get running in 5 minutes
30
+ - **[Configuration](./docs/getting-started/configuration.md)** - Environment and SDK configuration
31
+ - **[Authentication](./docs/getting-started/authentication.md)** - Authentication setup and patterns
32
+
33
+ ### 🔧 Core Services
34
+ - **[Authentication Service](./docs/services/auth.md)** - User authentication and authorization
35
+ - **[Product Service](./docs/services/product.md)** - Product catalog management
36
+ - **[Order Service](./docs/services/order.md)** - Order lifecycle management
37
+ - **[User Service](./docs/services/user.md)** - Customer and user management
38
+ - **[Payment Service](./docs/services/payment.md)** - Payment processing and invoicing
39
+ - **[CRM Service](./docs/services/crm.md)** - Customer relationship management
40
+
41
+ ### 🛠️ Extended Services
42
+ - **[Warehouse Service](./docs/services/warehouse.md)** - Inventory management
43
+ - **[Computing Service](./docs/services/computing.md)** - Cloud computing services
44
+ - **[Campaign Service](./docs/services/campaign.md)** - Marketing campaigns
45
+ - **[Image Service](./docs/services/image.md)** - Image and media management
46
+ - **[Upload Service](./docs/services/upload.md)** - File upload handling
47
+
48
+ ### 📖 Advanced Topics
49
+ - **[Error Handling](./docs/advanced/error-handling.md)** - Robust error handling patterns
50
+ - **[TypeScript Support](./docs/advanced/typescript.md)** - Full TypeScript integration
51
+ - **[Testing](./docs/advanced/testing.md)** - Testing your integration
52
+ - **[Performance](./docs/advanced/performance.md)** - Optimization and best practices
53
+
54
+ ### 💡 Examples & Patterns
55
+ - **[E-commerce Flow](./docs/examples/ecommerce-flow.md)** - Complete workflow examples
56
+ - **[Authentication Patterns](./docs/examples/auth-patterns.md)** - Auth implementation patterns
57
+ - **[Product Management](./docs/examples/product-management.md)** - Product handling examples
58
+ - **[Order Processing](./docs/examples/order-processing.md)** - Order workflow examples
59
+
60
+ ### 🔍 API Reference
61
+ - **[Complete API Reference](./docs/api/README.md)** - Full API documentation
62
+ - **[Type Definitions](./docs/api/types.md)** - TypeScript type definitions
63
+ - **[Interfaces](./docs/api/interfaces.md)** - Interface specifications
64
+
65
+ ## 🏗️ Architecture Overview
66
+
67
+ ```
68
+ Longvan SDK
69
+ ├── 🔐 Authentication Layer
70
+ ├── 🛍️ Core E-commerce Services
71
+ │ ├── Product Management
72
+ │ ├── Order Processing
73
+ │ ├── User Management
74
+ │ └── Payment Processing
75
+ ├── 🔧 Extended Services
76
+ │ ├── Warehouse & Inventory
77
+ │ ├── CRM & Customer Support
78
+ │ ├── Marketing & Campaigns
79
+ │ └── Media & File Management
80
+ └── 🚀 Infrastructure
81
+ ├── GraphQL Client
82
+ ├── REST API Client
83
+ ├── Error Handling
84
+ └── TypeScript Support
85
+ ```
86
+
87
+ ## Key Features
88
+
89
+ - **🎯 Type-Safe**: Full TypeScript support with comprehensive type definitions
90
+ - **🔌 Multi-Protocol**: Supports both GraphQL and REST APIs
91
+ - **🔐 Secure**: Built-in authentication and token management
92
+ - **⚡ Performance**: Optimized for speed with caching and batching
93
+ - **🛠️ Developer-Friendly**: Intuitive API design with excellent IntelliSense
94
+ - **📱 Cross-Platform**: Works in Node.js, browsers, and React Native
95
+ - **🧪 Well-Tested**: Comprehensive test suite with high coverage
96
+ - **📖 Well-Documented**: Extensive documentation with real-world examples
97
+
98
+ ## 🚀 Installation
99
+
100
+ ### Using npm
101
+ ```bash
102
+ npm install @longvansoftware/storefront-js-client
103
+ ```
104
+
105
+ ### Using yarn
106
+ ```bash
107
+ yarn add @longvansoftware/storefront-js-client
108
+ ```
109
+
110
+ ### Using pnpm
111
+ ```bash
112
+ pnpm add @longvansoftware/storefront-js-client
113
+ ```
114
+
115
+ ## ⚡ Quick Example
116
+
117
+ ```typescript
118
+ import { SDK } from '@longvansoftware/storefront-js-client';
119
+
120
+ // Initialize SDK
121
+ const sdk = new SDK('your-org-id', 'your-store-id', 'dev');
122
+
123
+ // Authenticate user
124
+ const loginResponse = await sdk.auth.login({
125
+ username: 'user@example.com',
126
+ password: 'password123'
127
+ });
128
+ sdk.setToken(loginResponse.accessToken);
129
+
130
+ // Browse products
131
+ const products = await sdk.product.getSimpleProducts({
132
+ keyword: 'laptop',
133
+ currentPage: 1,
134
+ maxResult: 20
135
+ });
136
+
137
+ // Create order
138
+ const order = await sdk.order.createOrder({
139
+ customer_id: loginResponse.partyId,
140
+ line_items: [{
141
+ product_id: products[0].id,
142
+ quantity: 1,
143
+ input_price: products[0].price
144
+ }]
145
+ }, 'web', false, loginResponse.partyId);
146
+
147
+ console.log('Order created:', order.id);
148
+ ```
149
+
150
+ ## 🌟 What's New in v2.9.0
151
+
152
+ - ✨ Enhanced TypeScript support with stricter types
153
+ - 🚀 Improved error handling and debugging capabilities
154
+ - 🔧 New utility services for better platform integration
155
+ - ⚡ Performance optimizations and caching improvements
156
+ - 🔒 Updated dependencies and security enhancements
157
+ - 📖 Comprehensive documentation with real-world examples
158
+
159
+ ## 🤝 Community & Support
160
+
161
+ - **📖 Documentation**: [Complete Documentation](./docs/README.md)
162
+ - **🐛 Issues**: [GitLab Issues](https://gitlab.longvan.vn/long-van-platform-2.0/website/storefront-js-client/-/issues)
163
+ - **💬 Discussions**: [GitLab Discussions](https://gitlab.longvan.vn/long-van-platform-2.0/website/storefront-js-client/-/issues)
164
+ - **📧 Support**: Contact the Longvan development team
165
+
166
+ ## 🚀 Contributing
167
+
168
+ We welcome contributions! Please see our [Contributing Guide](./docs/contributing/README.md) for details on:
169
+
170
+ - 🔧 Setting up the development environment
171
+ - 📝 Code style and conventions
172
+ - 🧪 Running tests and quality checks
173
+ - 📤 Submitting pull requests
174
+
175
+ ## 📄 License
176
+
177
+ This project is licensed under the ISC License - see the [LICENSE](./LICENSE) file for details.
178
+
179
+ ---
180
+
181
+ **Ready to get started?**
182
+ - 🚀 [Quick Start Guide](./docs/getting-started/quick-start.md)
183
+ - 📖 [Complete Documentation](./docs/README.md)
184
+ - 🔍 [API Reference](./docs/api/README.md)
185
+
186
+ **Need help?** Open an issue on [GitLab](https://gitlab.longvan.vn/long-van-platform-2.0/website/storefront-js-client/-/issues) or check our [documentation](./docs/README.md).
@@ -2,143 +2,143 @@
2
2
  Object.defineProperty(exports, "__esModule", { value: true });
3
3
  exports.CREATE_USER_DETAIL_MUTATION = exports.LINKING_USER_LOGIN_AND_USER_DETAIL_MUTATION = exports.UPDATE_PROFILE_MUTATION = exports.UPDATE_PASSWORD_MUTATION = exports.UPDATE_INFO_MUTATION = exports.RESET_PASSWORD_MUTATION = exports.VERIFY_CODE_MUTATION = exports.SEND_SMS_VERIFY_CODE_MUTATION = exports.REGISTER_MUTATION = exports.LOGIN_MUTATION = void 0;
4
4
  const graphql_tag_1 = require("graphql-tag");
5
- exports.LOGIN_MUTATION = (0, graphql_tag_1.gql) `
6
- mutation Login($loginRequest: LoginRequest!) {
7
- login(loginRequest: $loginRequest) {
8
- partyId
9
- orgId
10
- fullName
11
- email
12
- phone
13
- address
14
- identityNumber
15
- gender
16
- birthDate
17
- avatarUrl
18
- accessToken
19
- username
20
- orgPermissionsMap
21
- orgPositionsMap
22
- orgRolesMap
23
- }
24
- }
5
+ exports.LOGIN_MUTATION = (0, graphql_tag_1.gql) `
6
+ mutation Login($loginRequest: LoginRequest!) {
7
+ login(loginRequest: $loginRequest) {
8
+ partyId
9
+ orgId
10
+ fullName
11
+ email
12
+ phone
13
+ address
14
+ identityNumber
15
+ gender
16
+ birthDate
17
+ avatarUrl
18
+ accessToken
19
+ username
20
+ orgPermissionsMap
21
+ orgPositionsMap
22
+ orgRolesMap
23
+ }
24
+ }
25
25
  `;
26
- exports.REGISTER_MUTATION = (0, graphql_tag_1.gql) `
27
- mutation Register($orgId: String!, $registerRequest: RegisterRequest!) {
28
- register(orgId: $orgId, registerRequest: $registerRequest) {
29
- id
30
- partyId
31
- type
32
- username
33
- status
34
- accessToken
35
- }
36
- }
26
+ exports.REGISTER_MUTATION = (0, graphql_tag_1.gql) `
27
+ mutation Register($orgId: String!, $registerRequest: RegisterRequest!) {
28
+ register(orgId: $orgId, registerRequest: $registerRequest) {
29
+ id
30
+ partyId
31
+ type
32
+ username
33
+ status
34
+ accessToken
35
+ }
36
+ }
37
37
  `;
38
- exports.SEND_SMS_VERIFY_CODE_MUTATION = (0, graphql_tag_1.gql) `
39
- mutation SendSmsVerifyCode($orgId: String!, $username: String!) {
40
- sendSmsVerifyCode(orgId: $orgId, username: $username) {
41
- id
42
- code
43
- username
44
- timeExpired
45
- }
46
- }
38
+ exports.SEND_SMS_VERIFY_CODE_MUTATION = (0, graphql_tag_1.gql) `
39
+ mutation SendSmsVerifyCode($orgId: String!, $username: String!) {
40
+ sendSmsVerifyCode(orgId: $orgId, username: $username) {
41
+ id
42
+ code
43
+ username
44
+ timeExpired
45
+ }
46
+ }
47
47
  `;
48
- exports.VERIFY_CODE_MUTATION = (0, graphql_tag_1.gql) `
49
- mutation VerifyCode($orgId: String!, $verifyCodeRequest: VerifyCodeRequest!) {
50
- verifyCode(orgId: $orgId, verifyCodeRequest: $verifyCodeRequest)
51
- }
48
+ exports.VERIFY_CODE_MUTATION = (0, graphql_tag_1.gql) `
49
+ mutation VerifyCode($orgId: String!, $verifyCodeRequest: VerifyCodeRequest!) {
50
+ verifyCode(orgId: $orgId, verifyCodeRequest: $verifyCodeRequest)
51
+ }
52
52
  `;
53
- exports.RESET_PASSWORD_MUTATION = (0, graphql_tag_1.gql) `
54
- mutation ResetPassword(
55
- $orgId: String!
56
- $username: String!
57
- $newPassword: String!
58
- $accessToken: String!
59
- ) {
60
- resetPassword(
61
- orgId: $orgId
62
- username: $username
63
- newPassword: $newPassword
64
- accessToken: $accessToken
65
- )
66
- }
53
+ exports.RESET_PASSWORD_MUTATION = (0, graphql_tag_1.gql) `
54
+ mutation ResetPassword(
55
+ $orgId: String!
56
+ $username: String!
57
+ $newPassword: String!
58
+ $accessToken: String!
59
+ ) {
60
+ resetPassword(
61
+ orgId: $orgId
62
+ username: $username
63
+ newPassword: $newPassword
64
+ accessToken: $accessToken
65
+ )
66
+ }
67
67
  `;
68
- exports.UPDATE_INFO_MUTATION = (0, graphql_tag_1.gql) `
69
- mutation UpdateInfo(
70
- $orgId: String
71
- $accessToken: String
72
- $updateUserRequest: UpdateUserRequest
73
- $type: String
74
- $password: String
75
- ) {
76
- updateInfo(
77
- orgId: $orgId
78
- accessToken: $accessToken
79
- updateUserRequest: $updateUserRequest
80
- type: $type
81
- password: $password
82
- ) {
83
- partyId
84
- fullName
85
- email
86
- phone
87
- address
88
- identityNumber
89
- gender
90
- birthDate
91
- avatarUrl
92
- }
93
- }
68
+ exports.UPDATE_INFO_MUTATION = (0, graphql_tag_1.gql) `
69
+ mutation UpdateInfo(
70
+ $orgId: String
71
+ $accessToken: String
72
+ $updateUserRequest: UpdateUserRequest
73
+ $type: String
74
+ $password: String
75
+ ) {
76
+ updateInfo(
77
+ orgId: $orgId
78
+ accessToken: $accessToken
79
+ updateUserRequest: $updateUserRequest
80
+ type: $type
81
+ password: $password
82
+ ) {
83
+ partyId
84
+ fullName
85
+ email
86
+ phone
87
+ address
88
+ identityNumber
89
+ gender
90
+ birthDate
91
+ avatarUrl
92
+ }
93
+ }
94
94
  `;
95
- exports.UPDATE_PASSWORD_MUTATION = `
96
- mutation UpdatePassword($orgId: String!, $accessToken: String!, $currentPassword: String!, $newPassword: String!) {
97
- updatePassword(orgId: $orgId, accessToken: $accessToken, currentPassword: $currentPassword, newPassword: $newPassword)
98
- }
95
+ exports.UPDATE_PASSWORD_MUTATION = `
96
+ mutation UpdatePassword($orgId: String!, $accessToken: String!, $currentPassword: String!, $newPassword: String!) {
97
+ updatePassword(orgId: $orgId, accessToken: $accessToken, currentPassword: $currentPassword, newPassword: $newPassword)
98
+ }
99
99
  `;
100
- exports.UPDATE_PROFILE_MUTATION = (0, graphql_tag_1.gql) `
101
- mutation UpdateProfile(
102
- $userLoginId: String!
103
- $name: String!
104
- $phone: String!
105
- $email: String
106
- ) {
107
- updateProfile(
108
- userLoginId: $userLoginId
109
- name: $name
110
- phone: $phone
111
- email: $email
112
- )
113
- }
100
+ exports.UPDATE_PROFILE_MUTATION = (0, graphql_tag_1.gql) `
101
+ mutation UpdateProfile(
102
+ $userLoginId: String!
103
+ $name: String!
104
+ $phone: String!
105
+ $email: String
106
+ ) {
107
+ updateProfile(
108
+ userLoginId: $userLoginId
109
+ name: $name
110
+ phone: $phone
111
+ email: $email
112
+ )
113
+ }
114
114
  `;
115
- exports.LINKING_USER_LOGIN_AND_USER_DETAIL_MUTATION = (0, graphql_tag_1.gql) `
116
- mutation LinkingUserLoginAndUserDetail(
117
- $userLoginId: String!
118
- $partyId: String!
119
- ) {
120
- linkingUserLoginAndUserDetail(userLoginId: $userLoginId, partyId: $partyId)
121
- }
115
+ exports.LINKING_USER_LOGIN_AND_USER_DETAIL_MUTATION = (0, graphql_tag_1.gql) `
116
+ mutation LinkingUserLoginAndUserDetail(
117
+ $userLoginId: String!
118
+ $partyId: String!
119
+ ) {
120
+ linkingUserLoginAndUserDetail(userLoginId: $userLoginId, partyId: $partyId)
121
+ }
122
122
  `;
123
- exports.CREATE_USER_DETAIL_MUTATION = (0, graphql_tag_1.gql) `
124
- mutation CreateUserDetail($userLoginId: String!, $partnerId: String!) {
125
- createUserDetail(userLoginId: $userLoginId, partnerId: $partnerId) {
126
- partyId
127
- orgId
128
- fullName
129
- email
130
- phone
131
- address
132
- identityNumber
133
- gender
134
- birthDate
135
- avatarUrl
136
- accessToken
137
- username
138
- readyV2
139
- orgPermissionsMap
140
- orgPositionsMap
141
- orgRolesMap
142
- }
143
- }
123
+ exports.CREATE_USER_DETAIL_MUTATION = (0, graphql_tag_1.gql) `
124
+ mutation CreateUserDetail($userLoginId: String!, $partnerId: String!) {
125
+ createUserDetail(userLoginId: $userLoginId, partnerId: $partnerId) {
126
+ partyId
127
+ orgId
128
+ fullName
129
+ email
130
+ phone
131
+ address
132
+ identityNumber
133
+ gender
134
+ birthDate
135
+ avatarUrl
136
+ accessToken
137
+ username
138
+ readyV2
139
+ orgPermissionsMap
140
+ orgPositionsMap
141
+ orgRolesMap
142
+ }
143
+ }
144
144
  `;