StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8497374
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-12-13T22:51:00.503
FavoriteCount
0
LastActivityDate
2011-12-13T22:51:00.503
LastEditDate
LastEditorUserId
0
OwnerUserId
1094686
ParentId
8482106
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
First off, thanks to Tyrsius, Romias and eth0 for their suggestions. I decided that I didn't want to use the Id for a category and I didn't want to create a route handler as this isn't really solving the root issue. Instead I create a validation attribute called "UsedAsUrl", and applied this to my Category.Name in my domain model. This has the benefits of inbuilt validation (good for the end user) and good re-usability from a developer perspective. So my category model now looks like this (note the [UsedAsUrl] attribute): <pre><code>public class Category { [Key] [DatabaseGenerated(DatabaseGeneratedOption.Identity)] public int Id { get; set; } [Required] [UsedAsUrl] [MaxLength(50, ErrorMessage = "One word or groups of words please")] public string Name { get; set; } public virtual List<Post> Posts { get; set; } } </code></pre> And the attribute I created looks like this: <pre><code>using System; using System.ComponentModel.DataAnnotations; using System.Text.RegularExpressions; namespace CommonWebsiteUtilities.Attributes { [AttributeUsage(AttributeTargets.Field | AttributeTargets.Property, AllowMultiple = false, Inherited = true)] public class UsedAsUrlAttribute : ValidationAttribute { public UsedAsUrlAttribute() : base("Must not contain a slash with spaces either side") {} public override bool IsValid(object value) { var input = value.ToString(); var result = true; if (input.Contains("/")) { input = Regex.Replace(input, @"\s+", " "); if (input.Contains(" /")) result = false; if (input.Contains("/ ")) result = false; if (input.Contains(" / ")) result = false; } return result; } } } </code></pre> Now when I go to add a category: <img src="https://i.stack.imgur.com/5mIvX.png" alt="adding a category that I know will fail validation"> I get this response automatically: <img src="https://i.stack.imgur.com/NQVqR.png" alt="Failed response with validation"> JS doesn't yet work, but my controller can pick up on the model state and this is the response from it, so the attribute is working correctly. This basically checks for a slash with spaces on either / any side. Please note that this is not an exhaustive URL validator, but it will do for my current project. If anyone has any improvements, please let me know and I'll amend this answer. I'm not good with RegExp, so didn't derive from RegularExpressionAttribute, and also I didn't want to have to supply the error message from inside my model. This Attribute should really be built upon as more rules appear when using categories as URL parts.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POMVC 3 - Slashes and spaces in route
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USHoecuspocus
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POMVC 3 - Slashes and spaces in route
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.