Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / csf-dev/CSF.ORM issues and pull requests
#28 - To reduce code duplication, merge shared NHibernate implementation logic into a common project
Issue -
State: closed - Opened by craigfowler over 4 years ago
Labels: enhancement
#28 - To reduce code duplication, merge shared NHibernate implementation logic into a common project
Issue -
State: closed - Opened by craigfowler over 4 years ago
Labels: enhancement
#28 - To reduce code duplication, merge shared NHibernate implementation logic into a common project
Issue -
State: closed - Opened by craigfowler over 4 years ago
Labels: enhancement
#28 - To reduce code duplication, merge shared NHibernate implementation logic into a common project
Issue -
State: closed - Opened by craigfowler over 4 years ago
Labels: enhancement
#28 - To reduce code duplication, merge shared NHibernate implementation logic into a common project
Issue -
State: closed - Opened by craigfowler over 4 years ago
Labels: enhancement
#28 - To reduce code duplication, merge shared NHibernate implementation logic into a common project
Issue -
State: closed - Opened by craigfowler over 4 years ago
Labels: enhancement
#27 - To establish and dispose of ORM connections, an API must be created for connection and disposal
Issue -
State: closed - Opened by craigfowler over 4 years ago
Labels: enhancement
#27 - To establish and dispose of ORM connections, an API must be created for connection and disposal
Issue -
State: closed - Opened by craigfowler over 4 years ago
Labels: enhancement
#27 - To establish and dispose of ORM connections, an API must be created for connection and disposal
Issue -
State: closed - Opened by craigfowler over 4 years ago
Labels: enhancement
#27 - To establish and dispose of ORM connections, an API must be created for connection and disposal
Issue -
State: closed - Opened by craigfowler over 4 years ago
Labels: enhancement
#27 - To establish and dispose of ORM connections, an API must be created for connection and disposal
Issue -
State: closed - Opened by craigfowler over 4 years ago
Labels: enhancement
#27 - To establish and dispose of ORM connections, an API must be created for connection and disposal
Issue -
State: closed - Opened by craigfowler over 4 years ago
Labels: enhancement
#27 - To establish and dispose of ORM connections, an API must be created for connection and disposal
Issue -
State: closed - Opened by craigfowler over 4 years ago
Labels: enhancement
#26 - To avoid duplication, combine the persistence tester NHibernate implementation with the ORM one
Issue -
State: closed - Opened by craigfowler over 4 years ago
- 4 comments
Labels: enhancement
#26 - To avoid duplication, combine the persistence tester NHibernate implementation with the ORM one
Issue -
State: closed - Opened by craigfowler over 4 years ago
- 4 comments
Labels: enhancement
#26 - To avoid duplication, combine the persistence tester NHibernate implementation with the ORM one
Issue -
State: closed - Opened by craigfowler over 4 years ago
- 4 comments
Labels: enhancement
#26 - To avoid duplication, combine the persistence tester NHibernate implementation with the ORM one
Issue -
State: closed - Opened by craigfowler over 4 years ago
- 4 comments
Labels: enhancement
#25 - To test the code, coverage must be created for NHibernate 5
Issue -
State: closed - Opened by craigfowler over 4 years ago
- 1 comment
Labels: duplicate, enhancement
#25 - To test the code, coverage must be created for NHibernate 5
Issue -
State: closed - Opened by craigfowler over 4 years ago
- 1 comment
Labels: duplicate, enhancement
#25 - To test the code, coverage must be created for NHibernate 5
Issue -
State: closed - Opened by craigfowler over 4 years ago
- 1 comment
Labels: duplicate, enhancement
#25 - To test the code, coverage must be created for NHibernate 5
Issue -
State: closed - Opened by craigfowler over 4 years ago
- 1 comment
Labels: duplicate, enhancement
#25 - To test the code, coverage must be created for NHibernate 5
Issue -
State: closed - Opened by craigfowler over 4 years ago
- 1 comment
Labels: duplicate, enhancement
#25 - To test the code, coverage must be created for NHibernate 5
Issue -
State: closed - Opened by craigfowler over 4 years ago
- 1 comment
Labels: duplicate, enhancement
#25 - To test the code, coverage must be created for NHibernate 5
Issue -
State: closed - Opened by craigfowler over 4 years ago
- 1 comment
Labels: duplicate, enhancement
#24 - To ensure the library is working, test coverage should be reviewed
Issue -
State: closed - Opened by craigfowler over 4 years ago
- 1 comment
Labels: enhancement
#24 - To ensure the library is working, test coverage should be reviewed
Issue -
State: closed - Opened by craigfowler over 4 years ago
- 1 comment
Labels: enhancement
#24 - To ensure the library is working, test coverage should be reviewed
Issue -
State: closed - Opened by craigfowler over 4 years ago
- 1 comment
Labels: enhancement
#24 - To ensure the library is working, test coverage should be reviewed
Issue -
State: closed - Opened by craigfowler over 4 years ago
- 1 comment
Labels: enhancement
#24 - To ensure the library is working, test coverage should be reviewed
Issue -
State: closed - Opened by craigfowler over 4 years ago
- 1 comment
Labels: enhancement
#24 - To ensure the library is working, test coverage should be reviewed
Issue -
State: closed - Opened by craigfowler over 4 years ago
- 1 comment
Labels: enhancement
#23 - To avoid unwanted errors/warnings, CSF.PersistenceTester.NUnit should be decorated with NonTestAssemblyAttribute
Issue -
State: closed - Opened by craigfowler over 4 years ago
Labels: enhancement
#23 - To avoid unwanted errors/warnings, CSF.PersistenceTester.NUnit should be decorated with NonTestAssemblyAttribute
Issue -
State: closed - Opened by craigfowler over 4 years ago
Labels: enhancement
#23 - To avoid unwanted errors/warnings, CSF.PersistenceTester.NUnit should be decorated with NonTestAssemblyAttribute
Issue -
State: closed - Opened by craigfowler over 4 years ago
Labels: enhancement
#23 - To avoid unwanted errors/warnings, CSF.PersistenceTester.NUnit should be decorated with NonTestAssemblyAttribute
Issue -
State: closed - Opened by craigfowler over 4 years ago
Labels: enhancement
#23 - To avoid unwanted errors/warnings, CSF.PersistenceTester.NUnit should be decorated with NonTestAssemblyAttribute
Issue -
State: closed - Opened by craigfowler over 4 years ago
Labels: enhancement
#23 - To avoid unwanted errors/warnings, CSF.PersistenceTester.NUnit should be decorated with NonTestAssemblyAttribute
Issue -
State: closed - Opened by craigfowler over 4 years ago
Labels: enhancement
#23 - To avoid unwanted errors/warnings, CSF.PersistenceTester.NUnit should be decorated with NonTestAssemblyAttribute
Issue -
State: closed - Opened by craigfowler over 4 years ago
Labels: enhancement
#22 - To ensure code quality, the repository must be configured with sonar cube
Issue -
State: closed - Opened by craigfowler over 4 years ago
- 3 comments
Labels: enhancement, build/deployment
#22 - To ensure code quality, the repository must be configured with sonar cube
Issue -
State: closed - Opened by craigfowler over 4 years ago
- 3 comments
Labels: enhancement, build/deployment
#22 - To ensure code quality, the repository must be configured with sonar cube
Issue -
State: closed - Opened by craigfowler over 4 years ago
- 3 comments
Labels: enhancement, build/deployment
#22 - To ensure code quality, the repository must be configured with sonar cube
Issue -
State: closed - Opened by craigfowler over 4 years ago
- 3 comments
Labels: enhancement, build/deployment
#22 - To ensure code quality, the repository must be configured with sonar cube
Issue -
State: closed - Opened by craigfowler over 4 years ago
- 3 comments
Labels: enhancement, build/deployment
#22 - To ensure code quality, the repository must be configured with sonar cube
Issue -
State: closed - Opened by craigfowler over 4 years ago
- 3 comments
Labels: enhancement, build/deployment
#22 - To ensure code quality, the repository must be configured with sonar cube
Issue -
State: closed - Opened by craigfowler over 4 years ago
- 3 comments
Labels: enhancement, build/deployment
#21 - To avoid duplication, archive repositories which have been merged into this one
Issue -
State: closed - Opened by craigfowler over 4 years ago
Labels: documentation, enhancement, build/deployment
#21 - To avoid duplication, archive repositories which have been merged into this one
Issue -
State: closed - Opened by craigfowler over 4 years ago
Labels: documentation, enhancement, build/deployment
#21 - To avoid duplication, archive repositories which have been merged into this one
Issue -
State: closed - Opened by craigfowler over 4 years ago
Labels: documentation, enhancement, build/deployment
#20 - To allow for code differences, NHibernate libraries should be separated by major version
Issue -
State: closed - Opened by craigfowler over 4 years ago
Labels: enhancement, breaking, build/deployment
#20 - To allow for code differences, NHibernate libraries should be separated by major version
Issue -
State: closed - Opened by craigfowler over 4 years ago
Labels: enhancement, breaking, build/deployment
#20 - To allow for code differences, NHibernate libraries should be separated by major version
Issue -
State: closed - Opened by craigfowler over 4 years ago
Labels: enhancement, breaking, build/deployment
#20 - To allow for code differences, NHibernate libraries should be separated by major version
Issue -
State: closed - Opened by craigfowler over 4 years ago
Labels: enhancement, breaking, build/deployment
#20 - To allow for code differences, NHibernate libraries should be separated by major version
Issue -
State: closed - Opened by craigfowler over 4 years ago
Labels: enhancement, breaking, build/deployment
#20 - To allow for code differences, NHibernate libraries should be separated by major version
Issue -
State: closed - Opened by craigfowler over 4 years ago
Labels: enhancement, breaking, build/deployment
#20 - To allow for code differences, NHibernate libraries should be separated by major version
Issue -
State: closed - Opened by craigfowler over 4 years ago
Labels: enhancement, breaking, build/deployment
#19 - Develop standard convention-based mappings which match my conventions
Issue -
State: open - Opened by craigfowler over 7 years ago
- 2 comments
Labels: enhancement
#19 - Develop standard convention-based mappings which match my conventions
Issue -
State: open - Opened by craigfowler over 7 years ago
- 2 comments
Labels: enhancement
#18 - Upgrade to support further versions of NHibernate
Issue -
State: closed - Opened by craigfowler almost 5 years ago
- 2 comments
Labels: enhancement
#18 - Upgrade to support further versions of NHibernate
Issue -
State: closed - Opened by craigfowler almost 5 years ago
- 2 comments
Labels: enhancement
#18 - Upgrade to support further versions of NHibernate
Issue -
State: closed - Opened by craigfowler almost 5 years ago
- 2 comments
Labels: enhancement
#18 - Upgrade to support further versions of NHibernate
Issue -
State: closed - Opened by craigfowler almost 5 years ago
- 2 comments
Labels: enhancement
#18 - Upgrade to support further versions of NHibernate
Issue -
State: closed - Opened by craigfowler almost 5 years ago
- 2 comments
Labels: enhancement
#18 - Upgrade to support further versions of NHibernate
Issue -
State: closed - Opened by craigfowler almost 5 years ago
- 2 comments
Labels: enhancement
#18 - Upgrade to support further versions of NHibernate
Issue -
State: closed - Opened by craigfowler almost 5 years ago
- 2 comments
Labels: enhancement
#16 - Review NHibernate-related types with a view to splitting-away those which don't relate to the ORM API
Issue -
State: closed - Opened by craigfowler almost 5 years ago
- 1 comment
Labels: enhancement, breaking
#16 - Review NHibernate-related types with a view to splitting-away those which don't relate to the ORM API
Issue -
State: closed - Opened by craigfowler almost 5 years ago
- 1 comment
Labels: enhancement, breaking
#16 - Review NHibernate-related types with a view to splitting-away those which don't relate to the ORM API
Issue -
State: closed - Opened by craigfowler almost 5 years ago
- 1 comment
Labels: enhancement, breaking
#16 - Review NHibernate-related types with a view to splitting-away those which don't relate to the ORM API
Issue -
State: closed - Opened by craigfowler almost 5 years ago
- 1 comment
Labels: enhancement, breaking
#16 - Review NHibernate-related types with a view to splitting-away those which don't relate to the ORM API
Issue -
State: closed - Opened by craigfowler almost 5 years ago
- 1 comment
Labels: enhancement, breaking
#16 - Review NHibernate-related types with a view to splitting-away those which don't relate to the ORM API
Issue -
State: closed - Opened by craigfowler almost 5 years ago
- 1 comment
Labels: enhancement, breaking
#16 - Review NHibernate-related types with a view to splitting-away those which don't relate to the ORM API
Issue -
State: closed - Opened by craigfowler almost 5 years ago
- 1 comment
Labels: enhancement, breaking
#15 - To avoid developer confusion, the API for comparing entity identities should be simpler
Issue -
State: closed - Opened by craigfowler about 5 years ago
- 4 comments
Labels: documentation, enhancement, question
#15 - To avoid developer confusion, the API for comparing entity identities should be simpler
Issue -
State: closed - Opened by craigfowler about 5 years ago
- 4 comments
Labels: documentation, enhancement, question
#14 - To remove obsolete code, deprecated types should be removed
Issue -
State: closed - Opened by craigfowler over 4 years ago
- 1 comment
Labels: enhancement, breaking
#14 - To remove obsolete code, deprecated types should be removed
Issue -
State: closed - Opened by craigfowler over 4 years ago
- 1 comment
Labels: enhancement, breaking
#14 - To remove obsolete code, deprecated types should be removed
Issue -
State: closed - Opened by craigfowler over 4 years ago
- 1 comment
Labels: enhancement, breaking
#14 - To remove obsolete code, deprecated types should be removed
Issue -
State: closed - Opened by craigfowler over 4 years ago
- 1 comment
Labels: enhancement, breaking
#14 - To remove obsolete code, deprecated types should be removed
Issue -
State: closed - Opened by craigfowler over 4 years ago
- 1 comment
Labels: enhancement, breaking
#14 - To remove obsolete code, deprecated types should be removed
Issue -
State: closed - Opened by craigfowler over 4 years ago
- 1 comment
Labels: enhancement, breaking
#13 - To ensure guidance is correct, the README documentation should be reviewed and updated
Issue -
State: closed - Opened by craigfowler over 4 years ago
- 1 comment
#13 - To ensure guidance is correct, the README documentation should be reviewed and updated
Issue -
State: closed - Opened by craigfowler over 4 years ago
- 1 comment
#13 - To ensure guidance is correct, the README documentation should be reviewed and updated
Issue -
State: closed - Opened by craigfowler over 4 years ago
- 1 comment
#13 - To ensure guidance is correct, the README documentation should be reviewed and updated
Issue -
State: closed - Opened by craigfowler over 4 years ago
- 1 comment
#13 - To ensure guidance is correct, the README documentation should be reviewed and updated
Issue -
State: closed - Opened by craigfowler over 4 years ago
- 1 comment
#12 - To discover impact and a potential bug, identity and entity equality across class hierarchies should be investigated
Issue -
State: closed - Opened by craigfowler over 4 years ago
- 1 comment
Labels: bug, question
#12 - To discover impact and a potential bug, identity and entity equality across class hierarchies should be investigated
Issue -
State: closed - Opened by craigfowler over 4 years ago
- 1 comment
Labels: bug, question
#12 - To discover impact and a potential bug, identity and entity equality across class hierarchies should be investigated
Issue -
State: closed - Opened by craigfowler over 4 years ago
- 1 comment
Labels: bug, question
#12 - To discover impact and a potential bug, identity and entity equality across class hierarchies should be investigated
Issue -
State: closed - Opened by craigfowler over 4 years ago
- 1 comment
Labels: bug, question
#12 - To discover impact and a potential bug, identity and entity equality across class hierarchies should be investigated
Issue -
State: closed - Opened by craigfowler over 4 years ago
- 1 comment
Labels: bug, question
#11 - Delete deprecated types
Issue -
State: closed - Opened by craigfowler about 7 years ago
- 2 comments
#11 - Delete deprecated types
Issue -
State: closed - Opened by craigfowler about 7 years ago
- 2 comments
#11 - Delete deprecated types
Issue -
State: closed - Opened by craigfowler about 7 years ago
- 2 comments
#11 - Delete deprecated types
Issue -
State: closed - Opened by craigfowler about 7 years ago
- 2 comments
#11 - Delete deprecated types
Issue -
State: closed - Opened by craigfowler about 7 years ago
- 2 comments
#11 - Delete deprecated types
Issue -
State: closed - Opened by craigfowler about 7 years ago
- 2 comments
#10 - Write a documentation wiki, showing how these libraries are used
Issue -
State: closed - Opened by craigfowler almost 5 years ago
Labels: documentation, enhancement
#10 - Write a documentation wiki, showing how these libraries are used
Issue -
State: closed - Opened by craigfowler almost 5 years ago
Labels: documentation, enhancement
#10 - Write a documentation wiki, showing how these libraries are used
Issue -
State: closed - Opened by craigfowler almost 5 years ago
Labels: documentation, enhancement
#10 - Write a documentation wiki, showing how these libraries are used
Issue -
State: closed - Opened by craigfowler almost 5 years ago
Labels: documentation, enhancement
#10 - Write a documentation wiki, showing how these libraries are used
Issue -
State: closed - Opened by craigfowler almost 5 years ago
Labels: documentation, enhancement
#10 - Write a documentation wiki, showing how these libraries are used
Issue -
State: closed - Opened by craigfowler almost 5 years ago
Labels: documentation, enhancement