Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add even more 3rd party tools #395

Closed
ErikEJ opened this issue May 14, 2017 · 6 comments · Fixed by #646
Closed

Add even more 3rd party tools #395

ErikEJ opened this issue May 14, 2017 · 6 comments · Fixed by #646
Assignees
Labels
good first issue This issue should be relatively straightforward to fix.
Milestone

Comments

@ErikEJ
Copy link
Contributor

ErikEJ commented May 14, 2017

dotnet/efcore#3797 (comment)

dotnet/efcore#2341 (comment)

dotnet/efcore#795 (comment)

@ajcvickers ajcvickers added this to the 2.0.0 milestone Jun 16, 2017
@gnaeus
Copy link

gnaeus commented Oct 11, 2017

Hello! I created an extension EntityFramework.CommonTools

https://www.nuget.org/packages/EntityFrameworkCore.CommonTools

It provides three main features:

  • Expansion of IQueryable extension methods inside lambda expressions (example)
  • Application-level transaction logs (example)
  • Utility for storing complex types in JSON columns (example)

And I want to add some info about this extension to the EFCore docs.

@divega
Copy link
Contributor

divega commented Dec 23, 2017

For this too (like providers), I am thinking about having a single page listing all tools in a table rather than separate pages referenced in the index. It may make sense to do some house cleaning if some of the tools are not being maintained or useful.

@divega divega modified the milestones: 2.0.0, 2.1.0 Dec 23, 2017
@ErikEJ
Copy link
Contributor Author

ErikEJ commented Dec 23, 2017

Good idea - any starting point/template for the table?

@divega
Copy link
Contributor

divega commented Feb 15, 2018

@ErikEJ sorry for the long delay answering. I think having a table that normalizes the information on the existing extension pages would be a good starting point. It would be good to include a column for compatibility and a description.

@divega divega added the good first issue This issue should be relatively straightforward to fix. label Feb 15, 2018
@ErikEJ
Copy link
Contributor Author

ErikEJ commented Feb 15, 2018

Do you have an exsisting page I can use a inspiration/template?

@divega
Copy link
Contributor

divega commented Feb 27, 2018

@ErikEJ you may now want to check the new provider list. The PR was #632.

  • This should be similar, although the columns may be different.
  • There is the need to redirect stuff to the index.md containing the table.
  • Tables in markdown are better than html but still hard to manage. You may want to use some editor add in that automates markdown tables fixup. You may also want to use two monitors 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue This issue should be relatively straightforward to fix.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants