MrDave1999
Member of...
MrDave1999 has made 4 contributions so far during the 2023 holidays
- > 12/ 1 chore: Add Directory.Build.props file
- > 12/ 2 chore: Add Directory.Build.props file
- > 12/ 3 refactor: Add descriptive messages to validations of PluginAttribute
- > 12/ 4 Update README.md
- > 12/ 5
- > 12/ 6
- > 12/ 7
- > 12/ 8
- > 12/ 9
- > 12/ 10
- > 12/ 11
- > 12/ 12
- > 12/ 13
- > 12/ 14
- > 12/ 15
- > 12/ 16
- > 12/ 17
- > 12/ 18
- > 12/ 19
- > 12/ 20
- > 12/ 21
- > 12/ 22
- > 12/ 23
- > 12/ 24
-
> 12/ 25 Happy Holidays
chore: Add Directory.Build.props file
This file defines the target framework for all projects.
chore: Add Directory.Build.props file
This file defines the target framework for all projects.
refactor: Add descriptive messages to validations of PluginAttribute
It is true that a struct is instantiable and can also implement interfaces. Although one would think that the benefit would be that it avoids fewer allocations/deallocations by the garbage collector. However, this is not true, because the struct must be converted to an interface (reference ty...
refactor: Add descriptive messages to validations of PluginAttribute
It is true that a struct is instantiable and can also implement interfaces. Although one would think that the benefit would be that it avoids fewer allocations/deallocations by the garbage collector. However, this is not true, because...
Change private property to a private field
There is no utility in using a private property, because no additional logic is added in the getter.
Use the term `Entity` instead of `Model`
This change has been decided to avoid the use of the term Model, since new contributors may relate this term to other patterns such as MVC or MVVM. So it may cause confusion.
Added the models in the Models layer to have it in one place
The advantage of this is that you can easily know what the database schema (tables, primary keys, foreign keys, fields, relationships between tables) is without having to access each functionality.
Removed two appointment status: in process and in consultation
The appointment status used in any dental office are: scheduled, assisted, not assisted and canceled. The other two (in process and in consultation) are not as common and depend on the dental office.
Added the generic repository in the DataAccess layer
This change was decided because the generic repository is used as a superior abstraction for reading or writing (data access) from a data source.
Added the kinship in the choices
Resolves #68.
Removed two appointment status: in process and in consultation
The appointment status used in any dental office are: scheduled, assisted, not assisted and canceled. The other two (in process and in consultation) are not as common and depend on the dental office.
Change namespace to Personal Information to improve readability
This namespace was chosen because it is more descriptive than simply saying: Persons.
Fixed a spelling error in the word `appoinment`
The word 'appoinment' was replaced by 'appointment'. See also https://github.com/DentallApp/back-end/pull/90.
Change the namespace to SchedulingBySecretary to improve readability
This namespace was chosen because it is more descriptive than simply saying: AppointmentScheduling.
Removed `ISoftDeleteDto` interface
Some files and also this interface have been removed, in order not to have unnecessary things in the project, since they will not be used.
Added the `OfficeId` property in the `getAvailabilityHours` method
This property is required to verify if the appointment date is a holiday.
Added support for top-level statements
Resolves #75.
Added support for .NET 7.0 and EF Core 7.0
Resolves #67.
Fixed a spelling error in the word appoinment
Resolves #73.