StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
18631684
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-09-05T08:44:13.727
FavoriteCount
0
LastActivityDate
2014-06-22T15:56:57.137
LastEditDate
2014-06-22T15:56:57.137
LastEditorUserId
134076
OwnerUserId
134076
ParentId
18473096
PostTypeId
2
Score
24
ViewCount
0
LastEditorDisplayName
text
Body
<h2>The first obvious mistake:</h2> <p>You can't specify controller and template on the state while your using views. They are mutually exclusive...</p> <p>This is because when there is no "views" but a controller and template on the state, UI-Router automatically creates the "views" property and pulls those properties to an "empty" view...</p> <pre><code>.state('base', { abstract: true, templateUrl: 'views/base.html', //Can't do this views: { // when this is there. "search": { templateUrl: "views/search.html" } } }) </code></pre> <p>Instead do: </p> <pre><code>.state('base', { abstract: true, views: { "": { templateUrl: 'views/base.html' }, "search": { templateUrl: "views/search.html" } } }) </code></pre> <h2>Second problem:</h2> <p>How views targeting works with nested views etc. is not very logical, it may work well if you restrict your self to one view in one view all the way down, but ones you start working with multiple named views it all gets confusing... Add unnamed views on top and many people gets lost...</p> <p>The way views work in UI-Router is the worst part of UI-Router...</p> <p>Given you example I am not even entirely sure of the way to target the search view from your abstract parent state... Might be:</p> <pre><code>.state('base', { abstract: true, views: { "": { templateUrl: 'views/base.html' }, "search@base": { templateUrl: "views/search.html" } } }) </code></pre> <p>If it can even be made to work... Alternatively you can move the search view out of base.html, but I guess you added it in there for a reason.</p> <p>The whole view concept is the biggest reason why I ended up writing <a href="https://github.com/dotJEM/angular-routing">https://github.com/dotJEM/angular-routing</a> instead.</p>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POAngular UI Router - Views in an Inherited State
  singulars
  PostTypePostTypeId
  PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USJens
UserOwnerUserId
1. USJens
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POAngular UI Router - Views in an Inherited State
  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
  VTUpMod
2. 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.