Skip to content

Updates for 2.0.0 pre-release branch #47

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

Merged
merged 11 commits into from
Sep 21, 2015
Merged

Conversation

jordangray
Copy link
Member

Significant updates for the 2.0.0 pre-release branch.

- Moved some classes to more appropriate namespaces.
- Initial work on customisable serialisation.
- Added serialiser for ExpandoObjects.
- Streamlined unit tests with method to check all cells in generated
workbook.
- Default serialiser will always come after array of alternative
serialisers.
DefaultXlsxSerialiser now provides virtual methods that can be easily
overridden by other serialiser implementations.
Added functionality to create custom contract resolvers.
Added new contract resolver that allows per-request selection of
serialised properties.
Cut down unit test code by removing some dross.
- Changed ExcelFieldInfo to ExcelColumnInfo wherever it appears.
- Changed XlsxContractResolver to ColumnResolver wherever it appears.
- Added documentation to a few classes/properties that needed it. (Still
plenty more to go!)
Bumped assembly one minor version, from 1.0 to 1.1.
Updated version in assembly info for related projects in the solution.
Updated all NuGet packages to latest versions.
@jordangray jordangray self-assigned this Sep 21, 2015
@jordangray jordangray added this to the v2.0—flexibility milestone Sep 21, 2015
@jordangray
Copy link
Member Author

Hmm… there are a few breaking changes with this version.

  1. Moved core functionality to more specific namespaces, e.g. WebApiContrib.Formatting.Xlsx.ExcelColumnAttribute to WebApiContrib.Formatting.Xlsx.Attributes.ExcelColumnAttribute.
  2. Renamed a few classes that are mostly used internally, e.g. ExcelFieldInfo to ExcelColumnInfo.

The second one won't be so bad, but that first one could be a bit of a headache. Given that, I should really release this as 2.0.0-pre and accept that it might be a while till these features are in a release version. There are people who legitimately want these features, but it seems worse to break things for existing users.

I'll try to update the assembly version tonight then merge this. @ChrisMissal, I just looked up how to do a pre-release version of a package in NuGet and it's stupidly obvious (put -pre at the end of the patch number in the assembly info), so please disregard my silly question from last night if you saw it. Lemme know if you're happy doing a NuGet release some time this week. :)

Cleaned up assembly info, set version for NuGet to 2.0.0-pre.
@jordangray jordangray changed the title Updates for 1.1.0 pre-release branch Updates for 2.0.0 pre-release branch Sep 21, 2015
jordangray added a commit that referenced this pull request Sep 21, 2015
Updates for 2.0.0 pre-release branch
@jordangray jordangray merged commit d8ce6d9 into WebApiContrib:pre Sep 21, 2015
@balajichekka
Copy link

Hi Jordan,

how is it going with pre, any planned date for release?

@jordangray
Copy link
Member Author

Hey! I haven't had a chance to do much with it in a while, and there's a few issues I'd like to fix before the 2.0 release.

Realistically, given my limited free time for the past few months, I'm unlikely to get through them all for a few months; however, you can find the prerelease version on NuGet already, and I'd love to get some more feedback on it! I know it's a bit sketch using a prerelease version, but it's probably the best option if you need some of the newer stuff now.

(Feel totally free to help if you'd like! I can give you pointers if there's something you'd like to work on. No pressure whatsoever, just want to let you know the invitation's open. :) )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants