csharpfritz / corewiki Goto Github PK
View Code? Open in Web Editor NEWA simple ASP.NET Core wiki that we are working on during live coding streams
License: MIT License
A simple ASP.NET Core wiki that we are working on during live coding streams
License: MIT License
In All.cshtml we are using:
asp-route-id="@item.Id"
to form parameters for edit but in Edit.cshtml.cs we are trying to load using topic: SingleOrDefaultAsync(m => m.Topic == id)
We could edit Edit.cshtml.cs to take int Id as input, and remove first null check while chaning linq query to be SingleOrDefaultAsync(m => m.Id == id)
Logged in folks can edit and add content
Need to add search - full text search of content
Authors need a way to save their profile
Should the Pull Request Process section of contributing.md include a step to rebase their branch prior to a creating a Pull Request to ensure we don't run into this: #63 (comment)?
Comments for articles
Allow authors list your articles
Suggested Columns:
Show the number of views/ read for an article.
Timestamps are not being replaced by the site.js script on Edge (currently running v42.17133.1.0).
site.js generates an error:
SCRIPT438: Object doesn't support property or method 'Symbol.iterator'
on the line for (var ts of timeStamps)
Article topic should be the URL requested
Should by redirect to /Details. Correct?
As tabs are being used this should probably default to an individuals editors preference.
Suggests:
To prepare three environments to deploy application [DEV, HML and PRD] in AKS.
Suggested:
CoreWiki, seems to be simple to 10 users.
Now, let's imagine to 300mil users concurrents:
200.000 Queries concurrents (features search, track changes, article ratings
50.000 Updates concurrents (update comments, update images, update article ratings)
50.000 Inserts concurrents (add comments, add images, add article ratings)
My suggestions is:
OBS: See, I first think to change the database platform to SQL Server 2017. And both docker containers connected in another docker container with SQL Server 2017.
@csharpfritz, What do you think about that?
Currently we are using querystring to [edit]
and [delete]
an article. How to change the route to action/topic.
Ex:
@csharpfritz: I understand that for [Details]
, [Create]
and [LatestChanges]
is resolved. Correct?
We could have a feature, when creating or editing an article, to import a (.md) file and automatically fill the content field.
In header CoreWiki and Home has the same function. We suggest to remove the home menu.
RSS feed of recently changes articles
Need an easy way to create a link to another wiki page, even if that pages does not yet exist. Then an easy way to create that page from within the referring page. Something similar to how SharePoint wiki does this.
Might be nice to have an estimated read time for articles in the wiki.
Need to be able to reference an article using PascalCase and have it converted into a link to another article
When I type an very long text in the topic field an exception is displayed. I think it's the limite of URL address.
[TOPIC]
= HomePage dssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss ddddddddddddddddddddddddddddddddddd d d[Edit]
and [Create]
the same problem.As a minimum viable... this could just be a page that contains links to other pages
Please re-enable being able to edit the topic as some times you need to fix simple things like spelling mistakes. Now the wiki uses an id an as key I don't see any reason why we can't edit the article topics.
Needs another table with article, rating, date of rating, article version, some user information
A simple ASP.NET Core wiki that we are working on during live coding streams.
NOTE: This project is the result of some streams transmitted using TWITCH platform. To collaborate and understand the project, please see the follows streams:
Date | Topic |
---|---|
March 27, 2018 | From DevIntersection in Orlando, ASP.NET Core with guest Shayne Boyer |
March 29, 2018 | Back in Philly working on our new Wiki project - Start 00:52:50 |
April 5, 2018 | Building a Wiki with ASP.NET Core - Updating to Bootstrap 4 |
HomePage - It's not a page or a feature. This is a default article that is presented as if it were the Home. When the user navigate to /Details, if topicName is not specified, the application redirect to default Article (HomePage)
[Back to Home (CoreWiki)]
[LatestChanges]
[Create new article]
[Edit]
[Back to Home]
[Create]
[Back to Home]
[Back to Home]
[Edit]
[Delete]
[Detail]
[Create new article]
[Back to Home]
[Not Simulated]
.[Others ...]
Just tested the new UrlHelper with the following Article Topic (all the letters on my English keyboard):
--`~1!2@3#4$5%6^7&8*9(0)-_=+qQwWeErRtTyYuUiIoOpP[{]}\|aAsSdDfFgGhHjJkKlL;:'"zZxXcCvVbBnNmM,<.>/?--
and it creates the following url slug which does not work:
--`~1!2@3#4$5%6-7&8*9(0)--+qqwweerrttyyuuiioopp[{-}-|aassddffgghhjjkkll;:'"zzxxccvvbbnnmm-<->-?--
If I role back to the original UrlHelper that was created by the guys that run the SO site I get the following url slug that works properly:
123456-7890-qqwweerrttyyuuiioopp-aassddffgghhjjkkllzzxxcc
I think we need to rollback to the original UrlHelper as it has been tested on millions of stackoverflow pages & has also been tested with many other keyboards / languages.
Need to be able to upload images for articles
Doesn't route properly between pages
In different locations, we use different labels, for the same functionality:
Page | Label | Label (Suggested) | Comments |
---|---|---|---|
_Layout.cshtml | Create Page | [New article] |
|
LatestChanges.cshtml | Create New | [New article] |
We could think to remove, because it's duplicated. |
When use ASP.NET Core 2.1 or later, Microsoft recommends change the metapackage Microsoft.AspNetCore.All by Microsoft.AspNetCore.App.
<PackageReference Include = "Microsoft.AspNetCore.All" Version = "2.1.0"
<PackageReference Include = "Microsoft.AspNetCore.App"/>
<PackageReference Include="Microsoft.EntityFrameworkCore.Sqlite" Version="2.1.0" />
<DotNetCliToolReference Include="Microsoft.EntityFrameworkCore.Tools.DotNet" Version="2.0.1" />
If we remove the HomePage article the system doesn't work anymore.
In different locations, we use different labels, for the same functionality:
Page | Current | Suggested |
---|---|---|
Delete.cshtml | Back to Home Page | Back to Home |
Edit.cshtml | Back to List | Back to Home |
Create.cshtml | Back to List | Back to Home |
We should enable social logins as requested by banafys on stream
When I watched the Jeff's livestream at Build I noticed a bug in my code in the edit page. I did not check this correctly and both my fix and the code Jeff did on stage do not feel the right way to do this.
Currently we push a complete EF Entity to the Page, and actually populate (data-bind) a full EF Entity as well.
But, when we start to add properties we might not need alle properties in a page, so posting all that data to the page is unnecessary.
Also when we do not form submit fields that we have put attributes on in the EF Entity, but we don't care about in the PageModel we run into problems with the databinding not being able to populate the Entity.
My pull request had that problem because I did not have some of the added code from the project_VersionsAndRatins branche.
Using viewmodels that only push the fields needed and only require back the fields we can actually fill or care about elevates this. Not only that it allows us to abstract away from the EF decorated classes to classes more closely resembling POCO classes.
If we click the Submit button several times the comment is duplicated. How to avoid?
Suggested:
A history and list of changes to articles
Suggested by @bravecobra
This could be a configuration option, just like how Wordpress lets you choose comment engines
We could have an link in each article to navigate from LatestChanges to details page.
When I try to save an new article with the same name as an existing one, it presents an exception SQLite Error 19: 'UNIQUE constraint failed: Articles.Topic'.
EX:
I was watching the youtube video from the last stream (5-3-2018) and noticed at 2:19:40 that this js was giving a 404 in the developer tools. That is probably what is keeping the modelstate errors from displaying corrrectly.
This feels like a cool progressive web app waiting to happen!
We need an feature to list all articles. The feature LatestChanges list only 10 last published articles.
Suggested
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.