Add support for prefix of string collection fields#75
Conversation
|
Sounds good - go ahead and add a few unit tests to ensure it flows through nicely and we can probably get this into 1.4 |
|
@damieng I've added some tests -- basically same sort of tests that was there for On a side note: I was going to create a nuget package of my custom build and use it until 1.4 is out (to include this feature). However, using is there any specific way you produce your publishable nuget package? -- is ILMerge involved? |
|
I normally just use build packages. There were some recent changes to switch to NuGet only profile111 to allow it to be used on a variety of platforms. What dependency issue were you seeing? I'm going to see if we can get 1.4 out over the next few days. |
|
If there is no nightly dev builds by any chance, is there? |
|
Can you see if master at 5c031cf works fine for you with regards to the NuGet package? If it does we'll back out the Profile111 switch until after 1.4 in order to get this out quicker. |
Add support for prefix of string collection fields
|
The Profile111 work is backed out, let me know if that lets you create a nuget package without problem. |
|
Sure, will do and let you know. thanks :) |
|
@damieng Tested and all works perfectly 👍 |

I know unit-tests are yet to be done on this change, but I'm raising this early so we can have discussion around this.
In elastic search world, you can use
prefixfor bothstringfields andstring[]fields, but only the former is currently supported on elasticLINQ.this PR is adding support for the latter and it's surprizingly simple! :)
basically the entire expression mapping just works fine.
Please let me know what you think.