Contributing to PSKeePass

Considerations

1. Include comments on your code and keep them up to date.
2. Keep comments up to date.
3. Create issues for any code corrections or additions on the dev branch, fork then pull.
4. Use Allman Style indentation or at least be consistent with your style.
5. Run Pester Tests to verify your changes.
6. Create Pester Tests for new scenerios and functionality.
7. Ask questions via issues.

Needs Help

If you would like to contribute it would be great if you could focus on:

1. Exception/Error Handling
2. Module Help and Documentation
3. Pester Tests
4. Any Features you wish to add.

Working with the KeePassLib

Check out this auto generated doc at fossies.