Is there some kind linting that we could put into spotless (or a linting tool that’s run before spotless) to prevent this kind of thing (check against known proprietary names and derivatives before being allowed through ci)?
From: Jacob Barrett <jabarr...@vmware.com> Date: Tuesday, December 29, 2020 at 1:08 PM To: dev@geode.apache.org <dev@geode.apache.org> Subject: Re: State of https://github.com/apache/geode-dotnet-core-client Wow, that’s pretty bad that we put proprietary references into this repo from the start. If you have the bandwidth a cleanup PR would be appreciated. I can’t speak to the functionality but I would hope there are unit and integration tests that assert the supported behavior. -Jake > On Dec 21, 2020, at 4:48 PM, Michael Oleske <mole...@vmware.com> wrote: > > Hi Geode Dev Friends! > > I'm starting a personal little side project and was thinking of using Geode > as my backend (no real reason, certainly doesn't need the capabilities of > Geode, but thought it'd be fun.) I'm writing my application in .NET 5 (which > is core based) and was going to try and use > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode-dotnet-core-client&data=04%7C01%7Chutchisonjo%40vmware.com%7C804ce27cc1104f0a091408d8ac24ae83%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637448620864007534%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=XnxHxhZZD6dk2yZql2e%2FzpYmb%2FIwddJjQYWV7SqtKQo%3D&reserved=0 > > I see no one has really made any changes to it for a while, and that it seems > to have some proprietary references in it. Is it in a usable state for > simple puts/gets? > > -michael
