zydronium/google-nomulus
1
0
Fork 0
mirror of https://github.com/google/nomulus.git synced 2025-07-25 03:58:34 +02:00
Code Issues Projects Releases Packages Wiki Activity

Rename ContactResource -> Contact (#1763)

Browse source 
* Rename ContactResource -> Contact

This is a follow-up to PR #1725 and #1733. Now all EPP resource entity class
names have been rationalized to match with their SQL table names.
This commit is contained in:
Ben McIlwain 2022-08-29 14:48:32 -04:00 • committed by GitHub
parent b394341886
commit aacd834e16
116 changed files with 1118 additions and 1108 deletions
Download patch file Download diff file Expand all files Collapse all files

6
docs/architecture.md
View file

@ -327,7 +327,7 @@ registry codebase:
* `ClaimsList`, `ClaimsListShard`, and `ClaimsListSingleton` -- These entities
store the TMCH claims list, for use in trademark processing.
* `CommitLog*` -- These entities store the commit log information.
* `ContactResource` -- These hold the ICANN contact information (but not
* `Contact` -- These hold the ICANN contact information (but not
registrar contacts, who have a separate entity type).
* `Cursor` -- We use Cursor entities to maintain state about daily processes,
remembering which dates have been processed. For instance, for the RDE
@ -373,8 +373,8 @@ registry codebase:
* `Recurring` -- A Recurring is a billing event which represents a recurring
charge to the client (as opposed to OneTime).
* `Registrar` -- These hold information about client registrars.
* `RegistrarContact` -- Registrars have contacts just as domains do. These are
stored in a special RegistrarContact entity.
* `RegistrarPoc` -- Registrars have contacts just as domains do. These are
stored in a special RegistrarPoc entity.
* `Registry` -- These hold information about the TLDs supported by the
Registry system.
* `RegistryCursor` -- These entities are the predecessor to the Cursor

11
docs/code-structure.md
View file

@ -142,14 +142,9 @@ encapsulate related values together.
The classes that extend `EppResource` (along with the RFCs that define them) are
as follows:
* `Domain` ([RFC 5731](https://tools.ietf.org/html/rfc5731)), further
broken down into:
* `DomainApplication`, an application for a domain submitted during (e.g.)
sunrise or landrush
* `DomainResource`, a domain name allocated following a successful
application, or registered during a general availability phase
* `Domain` ([RFC 5731](https://tools.ietf.org/html/rfc5731))
* `Host` ([RFC 5732](https://tools.ietf.org/html/rfc5732))
* `ContactResource` ([RFC 5733](https://tools.ietf.org/html/rfc5733))
* `Contact` ([RFC 5733](https://tools.ietf.org/html/rfc5733))
All `EppResource` entities use a Repository Object Identifier (ROID) as its
unique id, in the format specified by [RFC
@ -173,7 +168,7 @@ Foreign key indexes provide a means of loading active instances of `EppResource`
objects by their unique IDs:
* `Domain`: fully-qualified domain name
* `ContactResource`: contact id
* `Contact`: contact id
* `Host`: fully-qualified host name
Since all `EppResource` entities are indexed on ROID (which is also unique, but