roles-privileges-payload-plugin 1.0.0 → 1.0.2
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 +1 -16
- package/package.json +28 -1
package/README.md
CHANGED
|
@@ -632,19 +632,4 @@ describe('Plugin tests', () => {
|
|
|
632
632
|
expect(...)
|
|
633
633
|
})
|
|
634
634
|
})
|
|
635
|
-
```
|
|
636
|
-
|
|
637
|
-
## Best practices
|
|
638
|
-
|
|
639
|
-
With this tutorial and the plugin template, you should have everything you need to start building your own plugin.
|
|
640
|
-
In addition to the setup, here are other best practices aim we follow:
|
|
641
|
-
|
|
642
|
-
- **Providing an enable / disable option:** For a better user experience, provide a way to disable the plugin without uninstalling it. This is especially important if your plugin adds additional webpack aliases, this will allow you to still let the webpack run to prevent errors.
|
|
643
|
-
- **Include tests in your GitHub CI workflow**: If you’ve configured tests for your package, integrate them into your workflow to run the tests each time you commit to the plugin repository. Learn more about [how to configure tests into your GitHub CI workflow.](https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-nodejs)
|
|
644
|
-
- **Publish your finished plugin to NPM**: The best way to share and allow others to use your plugin once it is complete is to publish an NPM package. This process is straightforward and well documented, find out more [creating and publishing a NPM package here.](https://docs.npmjs.com/creating-and-publishing-scoped-public-packages/).
|
|
645
|
-
- **Add payload-plugin topic tag**: Apply the tag **payload-plugin **to your GitHub repository. This will boost the visibility of your plugin and ensure it gets listed with [existing payload plugins](https://github.com/topics/payload-plugin).
|
|
646
|
-
- **Use [Semantic Versioning](https://semver.org/) (SemVar)** - With the SemVar system you release version numbers that reflect the nature of changes (major, minor, patch). Ensure all major versions reference their Payload compatibility.
|
|
647
|
-
|
|
648
|
-
# Questions
|
|
649
|
-
|
|
650
|
-
Please contact [Payload](mailto:dev@payloadcms.com) with any questions about using this plugin template.
|
|
635
|
+
```
|
package/package.json
CHANGED
|
@@ -1,9 +1,36 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "roles-privileges-payload-plugin",
|
|
3
|
-
"version": "1.0.
|
|
3
|
+
"version": "1.0.2",
|
|
4
4
|
"description": "Automatic role-based access control (RBAC) plugin for Payload CMS that generates granular CRUD privileges for all collections with beautiful UI and zero configuration",
|
|
5
|
+
"keywords": [
|
|
6
|
+
"payload",
|
|
7
|
+
"payload-cms",
|
|
8
|
+
"payload-plugin",
|
|
9
|
+
"payloadcms",
|
|
10
|
+
"roles",
|
|
11
|
+
"privileges",
|
|
12
|
+
"rbac",
|
|
13
|
+
"access-control",
|
|
14
|
+
"permissions",
|
|
15
|
+
"authorization",
|
|
16
|
+
"auth",
|
|
17
|
+
"user-roles",
|
|
18
|
+
"role-based",
|
|
19
|
+
"crud",
|
|
20
|
+
"admin",
|
|
21
|
+
"cms",
|
|
22
|
+
"content-management"
|
|
23
|
+
],
|
|
5
24
|
"author": "Hassine",
|
|
6
25
|
"license": "MIT",
|
|
26
|
+
"repository": {
|
|
27
|
+
"type": "git",
|
|
28
|
+
"url": "https://github.com/Hammoudahassine/roles-privileges-payload-plugin.git"
|
|
29
|
+
},
|
|
30
|
+
"bugs": {
|
|
31
|
+
"url": "https://github.com/Hammoudahassine/roles-privileges-payload-plugin/issues"
|
|
32
|
+
},
|
|
33
|
+
"homepage": "https://github.com/Hammoudahassine/roles-privileges-payload-plugin#readme",
|
|
7
34
|
"type": "module",
|
|
8
35
|
"exports": {
|
|
9
36
|
".": {
|