return rules.remove(rule);
        }

        @Override
        public boolean hasRule(Rule rule) {
            return rules.contains(rule);
        }
    }

    /**
     * Simple test rule implementation
     */
    public static class TestRule implements Rule {
        private static final long serialVersionUID = 1L;
        private final String ruleId;
        private final boolean matchResult;

            bb.putShort((short) 1); // numReferrals
            bb.putShort((short) 15); // tflags
            bb.putShort((short) 0); // tflags high bytes

            // Simple v1 referral
            bb.putShort((short) 1); // version
            bb.putShort((short) 16); // size
            bb.putShort((short) 1); // serverType
            bb.putShort((short) 2); // rflags

            return fileSystemInformationClass;
        }

        @Override
        public int decode(byte[] buffer, int bufferIndex, int len) throws jcifs.internal.SMBProtocolDecodingException {
            // Simple test implementation - not used in these tests
            return 0;
        }
    }

    @Nested
    @DisplayName("Interface Contract Tests")
    class InterfaceContractTests {

        @Test

```

</div>

## Create a Virtual Environment { #create-a-virtual-environment }

When you start working on a Python project **for the first time**, create a virtual environment **<abbr title="there are other options, this is a simple guideline">inside your project</abbr>**.

/// tip

You only need to do this **once per project**, not every time you work.

///

//// tab | `venv`

* **출력 모델** 은 비밀번호를 가지면 안됩니다.
* **데이터베이스 모델** 은 해시처리된 비밀번호를 가질 것입니다.

/// danger | 위험

절대 사용자의 비밀번호를 평문으로 저장하지 마세요. 항상 이후에 검증 가능한 "안전한 해시(secure hash)"로 저장하세요.

만약 이게 무엇인지 모르겠다면, [security chapters](security/simple-oauth2.md#password-hashing){.internal-link target=_blank}.에서 비밀번호 해시에 대해 배울 수 있습니다.

///

## 다중 모델

아래는 비밀번호 필드와 해당 필드가 사용되는 위치를 포함하여, 각 모델들이 어떤 형태를 가질 수 있는지 전반적인 예시입니다:

### Unlimited "plug-ins" { #unlimited-plug-ins }

Or in other way, no need for them, import and use the code you need.

Any integration is designed to be so simple to use (with dependencies) that you can create a "plug-in" for your application in 2 lines of code using the same structure and syntax used for your *path operations*.

### Tested { #tested }

            stemmerOverrideItemList = itemList;
        } catch (final IOException e) {
            throw new DictionaryException("Failed to parse " + path, e);
        }
    }

    /**
     * Returns the simple name of the dictionary file.
     *
     * @return The file name without the path.
     */
    public String getSimpleName() {
        return new File(path).getName();
    }

    /**

  private static final int NUM_THREADS = 10; // make a param?

  // simple interface to wrap our two implementations.
  interface ExecutionListWrapper {
    void add(Runnable runnable, Executor executor);

    void execute();

    /** Returns the underlying implementation, useful for the Footprint benchmark. */
    Object getImpl();
  }

  enum Impl {
    NEW {
      @Override
      ExecutionListWrapper newExecutionList() {

/// note

Dans ce cas-là, **FastAPI** ne vérifiera pas le contenu de la liste.

Par exemple, `List[int]` vérifiera (et documentera) que la liste est bien entièrement composée d'entiers. Alors qu'un simple `list` ne ferait pas cette vérification.

///

## Déclarer des métadonnées supplémentaires

On peut aussi ajouter plus d'informations sur le paramètre.

import jcifs.CIFSException;
import jcifs.ResourceNameFilter;
import jcifs.SmbResource;

@ExtendWith(MockitoExtension.class)
class DirFileEntryEnumIteratorBaseTest {

    // Simple FileEntry implementation used for tests
    private static FileEntry entry(String name) {
        return new FileEntry() {
            @Override
            public String getName() {
                return name;