Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / damieng/Linq.Translations issues and pull requests
#15 - Is there a way to extract the logic to be reused by different Model-Classes?
Issue -
State: open - Opened by bergerb-com 4 days ago
#14 - Migrate to .NET 6
Pull Request -
State: closed - Opened by damieng about 2 years ago
Labels: hacktoberfest-accepted
#13 - .NET Standard 2.0 compatible NuGet
Issue -
State: closed - Opened by neeohw over 4 years ago
- 1 comment
#12 - Switch to .NET Standard 2.0.
Pull Request -
State: closed - Opened by damieng over 5 years ago
#11 - Target .NET Standard 2.0 instead or in addition to 1.0?
Issue -
State: closed - Opened by divega over 5 years ago
- 3 comments
#10 - Create LICENSE
Pull Request -
State: closed - Opened by damieng over 6 years ago
- 2 comments
#9 - Switch to .NET Standard 1.0
Pull Request -
State: closed - Opened by damieng over 7 years ago
#8 - Target .NET Standard
Issue -
State: closed - Opened by divega over 7 years ago
#7 - Move back to csproj-based project
Issue -
State: closed - Opened by divega over 7 years ago
#6 - Potential enhancement to support overrides on translated attributes in derived classes
Pull Request -
State: closed - Opened by crocom almost 9 years ago
- 3 comments
#5 - updated to project.json based project system
Pull Request -
State: closed - Opened by milutinovici about 9 years ago
#4 - Make the library compatible with .NET Core
Issue -
State: closed - Opened by milutinovici about 10 years ago
#3 - Assembly in NuGet package is not strong named
Issue -
State: closed - Opened by bojingo over 11 years ago
- 1 comment
#2 - Is it possible to use translations for navigation properties?
Issue -
State: closed - Opened by AlexKeySmith over 12 years ago
- 3 comments
#1 - A possible way of triggering the expression without explicity calling the property?
Issue -
State: closed - Opened by AlexKeySmith over 12 years ago
- 7 comments