Skip to content

Commit cb0ffd3

Browse files
authored
Merge pull request #4 from Fellowmind/release/25.08.22
JS and pcf changes
2 parents 47ee883 + 9ccd0fc commit cb0ffd3

File tree

9 files changed

+231
-108
lines changed

9 files changed

+231
-108
lines changed

.gitignore

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -74,3 +74,5 @@ Actions/GenerateReferenceNumber/packages/
7474
/Fellowmind.PowerPlatform.DeveloperToolkit.JS.ConstantGenerator
7575
**/.vs
7676
*.sln
77+
PCF/README.md
78+
PCF/README.md

PCF/Hierarchy/HierarchyPCFControl/ControlManifest.Input.xml

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,8 @@
33
<control
44
namespace="Fellowmind"
55
constructor="HierarchyPCFControl"
6-
version="1.0.68"
6+
version="1.1.0"
7+
78
display-name-key="Hierarchy Control"
89
description-key="HierarchyPCFControl description"
910
control-type="standard"

PCF/OpenHierarchyButton/OpenHierarchyButton/ControlManifest.Input.xml

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,8 @@
11
<?xml version="1.0" encoding="utf-8" ?>
22
<manifest>
3-
<control namespace="Fellowmind" constructor="OpenHierarchyButton" version="0.0.1" display-name-key="OpenHierarchyButton" description-key="OpenHierarchyButton description" control-type="standard" >
3+
4+
<control namespace="Fellowmind" constructor="OpenHierarchyButton" version="1.0.0" display-name-key="OpenHierarchyButton" description-key="OpenHierarchyButton description" control-type="standard" >
5+
46
<!--external-service-usage node declares whether this 3rd party PCF control is using external service or not, if yes, this control will be considered as premium and please also add the external domain it is using.
57
If it is not using any external service, please set the enabled="false" and DO NOT add any domain below. The "enabled" will be false by default.
68
Example1:

PCF/PCFToolkit/PCFToolkit.cdsproj

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -58,6 +58,8 @@
5858
<ProjectReference Include="..\CustomDatePicker\Fellowmind.CustomDatePicker.pcfproj" />
5959
<ProjectReference Include="..\Year-picker\pcf.pcfproj" />
6060
<ProjectReference Include="..\RegexValidator\RegexValidationControl\Fellowmind.RegexValidator.pcfproj" />
61+
<ProjectReference Include="..\Hierarchy\HierarchyPCFControl.pcfproj" />
62+
<ProjectReference Include="..\OpenHierarchyButton\OpenHierarchyButton.pcfproj" />
6163
</ItemGroup>
6264

6365
<Import Project="$(MSBuildToolsPath)\Microsoft.Common.targets" />

PCF/README.md

Lines changed: 3 additions & 30 deletions
Original file line numberDiff line numberDiff line change
@@ -18,33 +18,6 @@ UNIVERSAL [email protected] Public User FMFI
1818

1919
### Publish for development
2020

21-
```bash
22-
pac auth create
23-
pac auth create --url https://fmfiproductdevelopment.crm4.dynamics.com/
24-
```
25-
26-
Update ControlManifest.Input.xml version
27-
28-
pac pcf push --publisher-prefix fmfi
29-
30-
### Publish for production
31-
The directory PCFToolkit contains the solution for production. Make sure to update the version in the ControlManifest.Input.xml file for each component.
32-
33-
You can use dotnet to publish the solution.
34-
35-
```bash
36-
dotnet build --configuration Release
37-
```
38-
39-
This will output the solution in the bin/Release folder.
40-
41-
If you want to get both the managed (production release) and the the unmanaged (for development) solution, you can use the following command:
42-
43-
```bash
44-
dotnet build --configuration Both
45-
```
46-
47-
This will output the solution in the bin/Both folder.
48-
49-
### IMPORTANT
50-
IMPORT ONLY UNMANAGED-solution to dev-environment. Otherwise components cannot be exported with the main FM Developer Kit -solution.
21+
PCF Components have DevOps-pipeline that is triggering from the master -branch and deploying latest version automatically to the development environment.
22+
https://dev.azure.com/godemo/FM%20Product%20development%20ALM/_build?definitionId=49
23+
Enjoy!

PCF/RegexValidator/RegexValidationControl/RegexValidator/ControlManifest.Input.xml

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,9 @@
11
<?xml version="1.0" encoding="utf-8"?>
22
<manifest>
33
<control namespace="Fellowmind" constructor="RegexValidator"
4-
version="1.0.2" display-name-key="FM Regex Validator"
4+
5+
version="1.2.7" display-name-key="FM Regex Validator"
6+
57
description-key="Apply Regex Validation on Text Field" control-type="standard">
68
<!--
79
A type-group to accept all required and supported Text Field Types
@@ -28,6 +30,9 @@
2830
<property name="notificationToUser" display-name-key="Field Notification"
2931
description-key="Field Notification To User. Default Message will be Incorrect Format."
3032
of-type="SingleLine.TextArea" usage="input" required="false" />
33+
<property name="validationEnabled" display-name-key="Validation Enabled"
34+
description-key="Enable or Disable Validation of Input Text. Default is true."
35+
of-type="TwoOptions" usage="input" required="false" default-value="true" />
3136

3237
<resources>
3338
<code path="index.ts" order="1" />

0 commit comments

Comments
 (0)