---
title: "Discussion on \"Obfuscating a Refit REST Client: What the Interface Attributes Pin, and What You Can Safely Rename\" | Hashnode"
description: "Discussion on \"Obfuscating a Refit REST Client: What the Interface Attributes Pin, and What You Can Safely Rename\". Most \"do not obfuscate this\" warnings are about serialization: the member name is the wire key, so renaming breaks it. Refit looks like it should be in that category — you hand it a C# interface and i"
url: "https://hashnode.com/posts/obfuscating-a-refit-rest-client-what-the-interface-attributes-pin-and-what-you-can-safely-rename/6af8928c4aebfdfe7ae18adf"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Obfuscating a Refit REST Client: What the Interface Attributes Pin, and What You Can Safely Rename](https://delta1labs.hashnode.dev/obfuscating-a-refit-rest-client-what-the-interface-attributes-pin-and-what-you-can-safely-rename?utm_source=hashnode&utm_medium=feed)

Most "do not obfuscate this" warnings are about serialization: the member name is the wire key, so renaming breaks it. Refit looks like it should be in that category — you hand it a C# interface and i

6h ago · 7 min read · delta1labs.hashnode.dev  
Read the article

-   [#refit](https://hashnode.com/tag/refit)
-   [#nebula](https://hashnode.com/tag/nebula)

## Written by

[Zero Heartbeat](https://hashnode.com/@clustron)

@clustron

  
[View profile](https://hashnode.com/@clustron)

## Responses

Markdown supported · ⌘↵ to post

No responses yet.