The guide wrote an empty subjectAlternativeNames for every domain it switched. A domain already on ACME isn't ticked by default, but ticking one wiped its custom list with no warning.
It now keeps the domain's list. The names check and the review step use the names that list orders, by the server's rule: a name without a dot gets the domain added, one with a dot is used as written. A domain with no list gets the defaults, as before.
Tested with a new orderNames case, plus typecheck, lint, i18n check, full npm test, the release-version and IPv6 scripts, build and notice check. I didn't click through the guide against a live server.
Fixes #160.
The guide wrote an empty `subjectAlternativeNames` for every domain it switched. A domain already on ACME isn't ticked by default, but ticking one wiped its custom list with no warning.
It now keeps the domain's list. The names check and the review step use the names that list orders, by the server's rule: a name without a dot gets the domain added, one with a dot is used as written. A domain with no list gets the defaults, as before.
Tested with a new `orderNames` case, plus typecheck, lint, i18n check, full `npm test`, the release-version and IPv6 scripts, build and notice check. I didn't click through the guide against a live server.
The guide wrote an empty subjectAlternativeNames for every domain it
switched, so ticking a domain already on ACME wiped its custom list with
no warning. It now keeps the list, and checks and shows the names that
list orders: a name without a dot gets the domain added, one with a dot
is used as written, the same as the server.
Fixes#160
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Fixes #160.
The guide wrote an empty
subjectAlternativeNamesfor every domain it switched. A domain already on ACME isn't ticked by default, but ticking one wiped its custom list with no warning.It now keeps the domain's list. The names check and the review step use the names that list orders, by the server's rule: a name without a dot gets the domain added, one with a dot is used as written. A domain with no list gets the defaults, as before.
Tested with a new
orderNamescase, plus typecheck, lint, i18n check, fullnpm test, the release-version and IPv6 scripts, build and notice check. I didn't click through the guide against a live server.