Rename namespaces from edu.stanford.spezikt to edu.stanford.spezi
Include missing core package in some modules defined in core directory and update the namespaces to edu.stanford.core.[module-name]
Update other SpeziKt occurrences
Updated java directories to kotlin
Updated spezi-module and spezi_module directories to modules
Updated applicationId of app module to edu.stanford.spezi.app - @Basler182 Please consider this as you will probably need to update in Firebase as well
:gear: Release Notes
Add a bullet point list summary of the feature and possible migration guides if this is a breaking change so this section can be added to the release notes.Include code snippets that provide examples of the feature implemented or links to the documentation if it appends or changes the public interface.
:books: Documentation
Please ensure that you properly document any additions in conformance to Spezi Documentation Guide.You can use this section to describe your solution, but we encourage contributors to document your reasoning and changes using in-line documentation.
:white_check_mark: Testing
Please ensure that the PR meets the testing requirements set by CodeCov and that new functionality is appropriately tested.This section describes important information about the tests and why some elements might not be testable.
:pencil: Code of Conduct & Contributing Guidelines
Namespace rename
:recycle: Current situation & Problem
Fixes #4
edu.stanford.spezikt
toedu.stanford.spezi
core
package in some modules defined incore
directory and update the namespaces toedu.stanford.core.[module-name]
SpeziKt
occurrencesjava
directories tokotlin
spezi-module
andspezi_module
directories tomodules
applicationId
ofapp
module toedu.stanford.spezi.app
- @Basler182 Please consider this as you will probably need to update in Firebase as well:gear: Release Notes
Add a bullet point list summary of the feature and possible migration guides if this is a breaking change so this section can be added to the release notes. Include code snippets that provide examples of the feature implemented or links to the documentation if it appends or changes the public interface.
:books: Documentation
Please ensure that you properly document any additions in conformance to Spezi Documentation Guide. You can use this section to describe your solution, but we encourage contributors to document your reasoning and changes using in-line documentation.
:white_check_mark: Testing
Please ensure that the PR meets the testing requirements set by CodeCov and that new functionality is appropriately tested. This section describes important information about the tests and why some elements might not be testable.
:pencil: Code of Conduct & Contributing Guidelines
By submitting creating this pull request, you agree to follow our Code of Conduct and Contributing Guidelines: