Skip to content
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

Create C# code snippets for bitfields #2607

Closed
sav-norem opened this issue Nov 27, 2023 · 5 comments
Closed

Create C# code snippets for bitfields #2607

sav-norem opened this issue Nov 27, 2023 · 5 comments

Comments

@sav-norem
Copy link

The redis.io webpage for bitfields needs the C# example as well. The python equivalent can be used to copy the setup and can be found here

The first line of the file needs to be the ID for the example - # EXAMPLE: bitfield_tutorial

Each separate section is delimited with a tag that you will need to copy exactly for it to appear in the correct place, ie.

# STEP_START bf
{code}                                    
# STEP_END

# HIDE_START, # HIDE_END, # REMOVE_START, and # REMOVE_END can be used for debugging and deleting keys. Hide will hide until a user expands the example, remove will only be seen in the source code and will never appear on the webpage.

@dwdougherty and I will be reviewing and tracking these issues - feel free to tag us with any questions

@mgravell
Copy link
Collaborator

Hmmm; somehow I think we've not added direct BITFIELD support yet, despite that being a 3.2 thing - we should fix thatz and I'm happy to repurpose this to do that. However, updating redis.io seems like a different repo, i.e. we literally can't do that from here

@sav-norem
Copy link
Author

@mgravell I can tag @uglide to explain how it all works, but I thought this was the appropriate repo since it works just fine from the NRedisStack - redis/NRedisStack#197 - here's one that Steve did to add in a different data type. Is NRedisStack the correct repo instead of this one?

@sav-norem
Copy link
Author

actually that probably means that NRedisStack is the only place it will work from - I'll move these over there.

@mgravell
Copy link
Collaborator

We should still add direct support - it is more efficient and obvious that having to use an extension.

@slorello89
Copy link
Collaborator

FYI @mgravell #2107 (never did get around to figuring out the API design)

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

No branches or pull requests

3 participants