piral-blazor 1.3.3-beta.6190 → 1.3.3-beta.6201
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 +7 -3
- package/package.json +3 -3
package/README.md
CHANGED
|
@@ -37,7 +37,7 @@ where `my-app-shell` should refer to the name of the NPM package of your app she
|
|
|
37
37
|
Exposing components looks like:
|
|
38
38
|
|
|
39
39
|
```cs
|
|
40
|
-
@attribute [
|
|
40
|
+
@attribute [PiralExtension("sample-page")]
|
|
41
41
|
|
|
42
42
|
<div>
|
|
43
43
|
<p>
|
|
@@ -58,9 +58,11 @@ Exposing components looks like:
|
|
|
58
58
|
}
|
|
59
59
|
```
|
|
60
60
|
|
|
61
|
+
For more details visit the [Piral.Blazor](https://github.com/smapiot/Piral.Blazor) repository.
|
|
62
|
+
|
|
61
63
|
## Architecture
|
|
62
64
|
|
|
63
|
-
Blazor with Piral works from two sides. We have the app shell's side and the side of the
|
|
65
|
+
Blazor with Piral works from two sides. We have the app shell's side and the side of the micro frontends. This package allows to connect both sides, by placing a set of shared functionality in the app shell.
|
|
64
66
|
|
|
65
67
|
|
|
66
68
|
|
|
@@ -94,6 +96,8 @@ There is only a single argument, which refers to the name of the exposed Blazor
|
|
|
94
96
|
|
|
95
97
|
::: summary: For pilet authors
|
|
96
98
|
|
|
99
|
+
**Note**: If you use the .NET template (and specifically the `Piral.Blazor.Tools` package) then the whole JavaScript code will be generated for you. There is nothing you will need to do - even though you can also manually extend the generated JavaScript module.
|
|
100
|
+
|
|
97
101
|
You can use the `fromBlazor` function from the Pilet API to convert your Blazor components to components usable by your Piral instance.
|
|
98
102
|
|
|
99
103
|
Example use:
|
|
@@ -133,7 +137,7 @@ export function setup(piral: PiletApi) {
|
|
|
133
137
|
|
|
134
138
|
In this case, you'll also have to install the `blazor` package. `piral-blazor` will use this under the hood to access the Blazor libraries.
|
|
135
139
|
|
|
136
|
-
To maximize compatibility, the major and minor version of the `blazor` package should correspond to the major and minor version of .NET Blazor you want to use (e.g., `blazor@3.2.x` will resolve to the .NET Blazor `3.2` release train). It should be noted that the patch level is not aligned. If a specific patch level is desired, consult the `blazor` package documentation.
|
|
140
|
+
To maximize compatibility, the major and minor version of the `blazor` package should correspond to the major and minor version of .NET Blazor you want to use (e.g., `blazor@3.2.x` will resolve to the outdated .NET Blazor `3.2` release train - more recent ones look like `blazor@7.0.0`). It should be noted that the patch level is not aligned. If a specific patch level is desired, consult the `blazor` package documentation.
|
|
137
141
|
|
|
138
142
|
:::
|
|
139
143
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "piral-blazor",
|
|
3
|
-
"version": "1.3.3-beta.
|
|
3
|
+
"version": "1.3.3-beta.6201",
|
|
4
4
|
"description": "Plugin for integrating Blazor components in Piral.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"piral",
|
|
@@ -67,7 +67,7 @@
|
|
|
67
67
|
"test": "echo \"Error: run tests from root\" && exit 1"
|
|
68
68
|
},
|
|
69
69
|
"devDependencies": {
|
|
70
|
-
"piral-core": "1.3.3-beta.
|
|
70
|
+
"piral-core": "1.3.3-beta.6201"
|
|
71
71
|
},
|
|
72
|
-
"gitHead": "
|
|
72
|
+
"gitHead": "6e9f4e6f83514b5c38960ce015e073efc668f3d6"
|
|
73
73
|
}
|