BUG? Model.Archive.Category - NULL
See original GitHub issueHi there,
I will try to be quick for this one.
So I think that when I go to the URL:
localhost:5000/myArchive/category/special/
I should be getting the category as well in
@Model.Archive.Category
, but because this is null, so are the Slug&Title.
By looking at that:
I think that they have to be there, but are not set? Is this something not implemented, a weird bug or just me not understanding how it works? Because the posts in that archive have their category
set + you can get all the categories with await api.Posts.GetAllCategoriesAsync(Id)
.
The whole point of this is to be able to get the current category that we have have in the URL in our Model, so I can use it.
Regards, Chris
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
Bug Update: Filtering on Null Values
Past May @SamEich posted a bug regarding Null values. Basically the filters you add to a Domo card are not able to filter...
Read more >Null or unobserved categories: structural and incidental ...
Structural null categories occur when rating scale categories are number 10, 20, ... Another approach is to model the categories with a polynomial...
Read more >Can I change category_id of images to null on deletion ...
I have 2 tables - images and categories . The images table has a column called category_id which takes the id of the...
Read more >Bug descriptions — spotbugs 4.7.3 documentation
This finalizer nulls out fields. This is usually an error, as it does not aid garbage collection, and the object is going to...
Read more >Error / bug in brms models? - The Stan Forums
My models don't seem to run, and I get the error: running command ... CMD config CXX14 2>/dev/null' had status 72 I recently...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
DynamicPosts
are never cached, meaning that each time you request them a new object instance will be created. CallingIndexOf
on a generic list will only compare the actual pointers of the object, and since they are unique instances the index should be-1
. The reason why it works withPostInfo
is that this model type is cached, so both requests are in fact returning the same instance of the post.Best regards
Closing as this is fixed in master