7 commits

Author	SHA1	Message	Date
guyben	89c942b0d9	Have a resource component receive the "registrar resource" instead of creating it ... We have several "consoles" ("views" in the registrar console). They all affect the same resource - the registrar itself. Currently, each view creates its own "RESTful resource", even though it's the same resource for all of them, meaning we have copied code and copied "URL endpoint" across multiple files. I assume this was made so that IF one day we have a "view" to another resource, we can easily add it. But we currently don't have any such view, nor plans to add any. So according to the YAGNI paradigm, it's better to move the resource creation outside of the console. Also, IF we do add a view to a different resource - it'll still be more readable to have a map from the "view" to the "resource URL endpoint" alongside the existing map from the "view" to the "console"... ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=213992967	2018-10-03 11:49:01 -04:00
mmuller	b70f57b7c7	Update copyright year on all license headers ... ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=146111211	2017-02-02 16:27:22 -05:00
mmuller	2e4273c4f4	Genericize Google Drive Links ... Replace the two drive links on the "contact us" page with values that can be driven from the config. The drive links are the link to the technical documentation folder and the link to the registrar's transaction activity reports. The former is a straightforward static replacement, but the latter is derived from a per-registrar Google Drive id which must be formatted using a template from the config module. Note: This currently requires adding the transaction activity URL template to the old-style RegistryConfig class instead of the daggerized ConfigModule because this is the easiest way to pass it though to the non-daggerized RegistrarServlet. In an upcoming CL, I'll convert RegistrarServlet to RegistrarAction and then I'll be able to make this template injectable. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=137518466	2016-11-02 15:19:34 -04:00
mmuller	84bbb9a7c0	Genericize "Contact Us" page ... Parameterize integration, support and announcement email addresses and contact phone number, make static parameters flow through the system in a consistent manner. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=136183813	2016-10-14 17:41:55 -04:00
shikhman	f76bc70f91	Preserve test logs and test summary output for Kokoro CI runs ... ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=135494972	2016-10-14 16:57:43 -04:00
jart	7b9752c99d	Forward declare namespaces only in JSDoc ... Forward declares symbol. This is an indication to the compiler that the symbol may be used in the source yet is not required and may not be provided in compilation. The most common usage of forward declaration is code that takes a type as a function parameter but does not need to require it. By forward declaring instead of requiring, no hard dependency is made, and (if not required elsewhere) the namespace may never be required and thus, not be pulled into the JavaScript binary. If it is required elsewhere, it will be type checked as normal. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=127095620	2016-07-13 15:57:11 -04:00
Justine Tunney	5012893c1d	mv com/google/domain/registry google/registry ... This change renames directories in preparation for the great package rename. The repository is now in a broken state because the code itself hasn't been updated. However this should ensure that git correctly preserves history for each file.	2016-05-13 18:55:08 -04:00

Renamed from java/com/google/domain/registry/ui/js/registrar/contact_us.js (Browse further)