Paul Schneider
1b289c1387
When commit 0e95e283 moved BlogPost from PostIt.Models to
Yavsc.Blogspot, it created an unfortunate collision with the
server-side EF entity Yavsc.Models.Blog.BlogPost. The two
classes have nothing in common beyond the name; the DTO is
the wire shape PostIt exchanges with the Blogs API, the EF
entity is the persistence model. Server code that imports both
namespaces (BlogSpotService.cs, etc.) ended up with 'BlogPost
is an ambiguous reference between X and Y' errors.
Renaming the client DTO to BlogPostDto (matching the
naming convention of the other DTOs in Yavsc.Api.Client.Dtos
— CircleDto, CircleAuthorizationDto, UserSearchResultDto)
disambiguates without renaming the EF entity on the server.
The namespace stays Yavsc.Blogspot; only the class name
changes. All call sites (client code, tests, XAML DataTemplates,
XML doc comments) are updated mechanically.
36 lines
873 B
C#
36 lines
873 B
C#
using System;
|
|
using Yavsc.Abstract.Identity;
|
|
using Yavsc.Abstract.Identity.Security;
|
|
|
|
namespace Yavsc.Blogspot;
|
|
|
|
public class BlogPostDto : IBlogPost
|
|
{
|
|
public string AuthorId { get; set; }
|
|
|
|
public IApplicationUser Author { get; set; }
|
|
|
|
public string Article { get; set ; }
|
|
public string Photo { get; set ; }
|
|
public long Id { get; set; }
|
|
public DateTime DateCreated { get; set; }
|
|
public string UserCreated { get; set; }
|
|
public DateTime DateModified { get; set; }
|
|
public string UserModified { get; set; }
|
|
public string Title { get; set; }
|
|
|
|
public bool AuthorizeCircle(long circleId)
|
|
{
|
|
throw new NotImplementedException();
|
|
}
|
|
|
|
public ICircleAuthorization[] GetACL()
|
|
{
|
|
throw new NotImplementedException();
|
|
}
|
|
|
|
public string[] GetTags()
|
|
{
|
|
throw new NotImplementedException();
|
|
}
|
|
}
|