Extending field type list

Hey, At the moment, I have struggles to add custom field codes because the enum does not contain the whole list of field codes, but only a subset: https://github.com/EvotecIT/OfficeIMO/blob/master/OfficeIMO.Word/WordField.cs#L10

E.g., could we add BIBLIOGRAPHY to it? See: https://support.microsoft.com/en-us/office/field-codes-bibliography-field-cbb17838-05d7-4533-8066-4791aeddb9de

Some field codes require switches, so how about passing a dictionary to AddField(...) as an optional argument?

Do you think that is doable? Do you prefer a PR or to do it yourself?

[byteSamurai]

Let me put it this way: It’s refreshing to see a maintainer who is open to contributions. I saw exciting projects on Github, but the maintainers were very biased about their code quality. If you see a larger project w/o testing and the maintainer don’t wants to change anything because it’s so “well-crafted”, … don’t use it! However, I saw some magic strings/numbers in the parsing of the field codes. I am about to refactor this part at the moment. Looking forwarding hearing your opinion about it once I have done it. 💪🏻

[PrzemyslawKlys]

Hi,

• I have Windows 11 with Visual Studio 2022 Enterprise
• .NET Standard 2.0 and .NET Standard 2.1 is supported, and quite a lot of frameworks are supported - it’s windows,linux and maos so should work fine for you

It’s actually very useful for PowerShell where with one LIB you are able to support both PS 5.1 and PS 7 which is the main reason I created this project.

As you can see in the project there are 3 systems tested on Azure Devops - linux, windows, macos. As long as we retain tests for all supported frameworks on all supported systems we can adjust the settings to be runnable on all systems as required. Maybe it just needs some IF/ELSE in the configuration settings depending on OS version.