You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
3.Start a fresh new PowerShell session to avoid anythjing from your current working sessions to interfere with the module development and building. Develop your updates in the source directory.
36
36
37
-
You should also resolve all dependencies before you start developing. This will ensure that you have all the required modules installed and loaded into your session.
37
+
You should also resolve all dependencies before you start developing. This will ensure that you have all the required modules, and only them, installed and loaded into your session.
@@ -83,7 +83,11 @@ The workflow for using this and developing the code is shown below.
83
83
```PowerShell
84
84
./build.ps1 -Tasks build,test
85
85
```
86
-
8. Once you are ready to submit your changes for review please ensure that you update the `CHANGELOG.md` file with a summary of your changes. This is important as it helps us keep track of what has changed in the module and makes it easier for users to see what has been added or changed.
86
+
This will run all the tests in the `tests` folder and output the results to the console. If there are any issues with the code, they will be reported here.
87
+
88
+
8. It is always a good idea to develop in a brand new clean session and also once you have finished your changes, you should open a new session, build the module and run a few commands to ensure that everything is working as expected. This will help you catch any issues that may have been introduced during development and also make sure that you have not missed any dependancies.
89
+
90
+
9. Once you are ready to submit your changes for review please ensure that you update the `CHANGELOG.md` file with a summary of your changes. This is important as it helps us keep track of what has changed in the module and makes it easier for users to see what has been added or changed.
87
91
88
92
You can use the [Keep a Changelog](https://keepachangelog.com/en/1.0.0/) format for this.
-**Frank Geisler** - *Author of RTI functions* - [Frank Geisler](https://github.com/Frank-Geisler)
95
97
-**Kamil Nowinski** - *Refactoring, unification, further commands* - [NowinskiK](https://github.com/NowinskiK)
98
+
-**Jess Pomfret** - *Automation, great experience with PowerShell* - [jpomfret](https://github.com/jpomfret)
99
+
-**Rob Sewell** - *Automation/DevOps, Governance and experience brought from dbatools* - [SQLDBAWithABeard](https://github.com/SQLDBAWithABeard)
96
100
97
101
See also the list of [contributors](https://github.com/dataplat/FabricTools/contributors) who participated in this project.
98
102
@@ -103,4 +107,5 @@ This project is licensed under the MIT License - see the [LICENSE](LICENSE) file
103
107
## Acknowledgments
104
108
105
109
- GitHub Copilot and ChatGPT for helping with the documentation
106
-
-[**Rui Romano**](https://github.com/RuiRomano) - His work on a [Fabric PowerShell module](https://github.com/RuiRomano/fabricps-pbip) has been included into this module with his permission. Thanks, Rui!
110
+
-[**Rui Romano**](https://github.com/RuiRomano) - His work on a [Fabric PowerShell module](https://github.com/microsoft/Analysis-Services/tree/master/pbidevmode/fabricps-pbip) has been included into this module with his permission. Thanks, Rui!
111
+
-[**Tiago Balabuch**](https://github.com/tiagobalabuch) and his phenomenal huge work that make this module more robust and very well organised.
0 commit comments