baarkerlounger
/
submit-social-housing-lettings-and-sales-data
mirror of https://github.com/communitiesuk/submit-social-housing-lettings-and-sales-data.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
Submit social housing lettings and sales data (CORE)
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
1313 Commits
233 Branches
250 Tags
74 MiB
Tree: 04760076a5
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '04760076a5'
${ noResults }
submit-social-housing-letti.../config/locales/devise.en.yml

69 lines
4.2 KiB
Raw Normal View History Unescape

Add devise gem and a first test for user login Devise is a commonly used gem for user authentication and management. Using rails generators and Devise allows us to get a lot of boilerplate code for user authentication and management and means we don't have to revinvent the wheel. Styling will need to be done for the necessary pages and there are likely to be bits of generated code that can be deleted. This will act as a starting point to be built up from using TDD.
3 years ago
# Additional translations at https://github.com/heartcombo/devise/wiki/I18n
en:
devise:
confirmations:
Update devise translation strings (#461)
3 years ago
confirmed: "Your email address has been successfully confirmed"
send_instructions: "You will receive an email with instructions for how to confirm your email address in a few minutes"
send_paranoid_instructions: "If your email address exists in our database, you will receive an email in a few minutes with instructions for how to confirm your email address"
Add devise gem and a first test for user login Devise is a commonly used gem for user authentication and management. Using rails generators and Devise allows us to get a lot of boilerplate code for user authentication and management and means we don't have to revinvent the wheel. Styling will need to be done for the necessary pages and there are likely to be bits of generated code that can be deleted. This will act as a starting point to be built up from using TDD.
3 years ago
failure:
Update devise translation strings (#461)
3 years ago
already_authenticated: "You are already signed in"
inactive: "Your account has not been activated yet"
invalid: "Incorrect %{authentication_keys} email or password"
Update devise.en.yml
3 years ago
locked: "Your account has been locked."
Update devise translation strings (#461)
3 years ago
last_attempt: "You have one more attempt before your account is locked"
not_found_in_database: "Incorrect %{authentication_keys} email or password"
timeout: "Your session expired. Sign in again to continue."
unauthenticated: "You need to sign in or sign up before continuing"
unconfirmed: "You must confirm your email address before continuing"
Add devise gem and a first test for user login Devise is a commonly used gem for user authentication and management. Using rails generators and Devise allows us to get a lot of boilerplate code for user authentication and management and means we don't have to revinvent the wheel. Styling will need to be done for the necessary pages and there are likely to be bits of generated code that can be deleted. This will act as a starting point to be built up from using TDD.
3 years ago
mailer:
confirmation_instructions:
subject: "Confirmation instructions"
reset_password_instructions:
subject: "Reset password instructions"
unlock_instructions:
subject: "Unlock instructions"
email_changed:
Update devise translation strings (#461)
3 years ago
subject: "Email successfully changed"
Add devise gem and a first test for user login Devise is a commonly used gem for user authentication and management. Using rails generators and Devise allows us to get a lot of boilerplate code for user authentication and management and means we don't have to revinvent the wheel. Styling will need to be done for the necessary pages and there are likely to be bits of generated code that can be deleted. This will act as a starting point to be built up from using TDD.
3 years ago
password_change:
Update devise translation strings (#461)
3 years ago
subject: "Password successfully changed"
Add devise gem and a first test for user login Devise is a commonly used gem for user authentication and management. Using rails generators and Devise allows us to get a lot of boilerplate code for user authentication and management and means we don't have to revinvent the wheel. Styling will need to be done for the necessary pages and there are likely to be bits of generated code that can be deleted. This will act as a starting point to be built up from using TDD.
3 years ago
omniauth_callbacks:
Update devise translation strings (#461)
3 years ago
failure: "We could not authenticate you from %{kind} because \"%{reason}\""
success: "Successfully authenticated from %{kind} account"
Add devise gem and a first test for user login Devise is a commonly used gem for user authentication and management. Using rails generators and Devise allows us to get a lot of boilerplate code for user authentication and management and means we don't have to revinvent the wheel. Styling will need to be done for the necessary pages and there are likely to be bits of generated code that can be deleted. This will act as a starting point to be built up from using TDD.
3 years ago
passwords:
Update devise translation strings (#461)
3 years ago
no_token: "You can’t access this page unless you’re trying to reset your password. Check you’re using the correct URL in the email we sent you."
send_instructions: "You will receive an email in a few minutes with instructions on how to reset your password"
send_paranoid_instructions: "If your email address exists in our database, you will receive an email in the next few minutes with a link to recover your password"
updated: "Your password has been successfully changed. You are now signed in."
updated_2FA: "Your password has been successfully changed. We’ve sent you a security code."
updated_not_active: "Your password has been successfully changed"
Add devise gem and a first test for user login Devise is a commonly used gem for user authentication and management. Using rails generators and Devise allows us to get a lot of boilerplate code for user authentication and management and means we don't have to revinvent the wheel. Styling will need to be done for the necessary pages and there are likely to be bits of generated code that can be deleted. This will act as a starting point to be built up from using TDD.
3 years ago
registrations:
Update devise translation strings (#461)
3 years ago
destroyed: "Your account has been successfully cancelled"
signed_up: "You have successfully signed up for an account"
signed_up_but_inactive: "You have successfully signed up for an account. You won’t be able to sign in until your account is activated."
signed_up_but_locked: "You have successfully signed up for an account. We could not sign you in because your account is locked."
signed_up_but_unconfirmed: "We’ve sent a confirmation link to your email address. Follow the link to activate your account."
update_needs_confirmation: "You successfully updated your account. We need to verify your new email address. Check your email and follow the confirmation link to confirm your new email address."
updated: "Your account has been successfully updated"
updated_but_not_signed_in: "Your account has been successfully updated. You’ll need to sign in again."
Set sign in and sign out messages to empty strings (#161) * Set sign in and sign out messages to empty strings * Remove irrelevant test expectation
3 years ago
sessions:
signed_in: ""
signed_out: ""
already_signed_out: ""
Add devise gem and a first test for user login Devise is a commonly used gem for user authentication and management. Using rails generators and Devise allows us to get a lot of boilerplate code for user authentication and management and means we don't have to revinvent the wheel. Styling will need to be done for the necessary pages and there are likely to be bits of generated code that can be deleted. This will act as a starting point to be built up from using TDD.
3 years ago
unlocks:
Update devise translation strings (#461)
3 years ago
send_instructions: "You will receive an email in a few minutes with instructions for how to unlock your account"
send_paranoid_instructions: "If your account exists, you will receive an email in a few minutes with instructions for how to unlock it"
unlocked: "Your account has been successfully unlocked. Sign in to continue."
Add devise gem and a first test for user login Devise is a commonly used gem for user authentication and management. Using rails generators and Devise allows us to get a lot of boilerplate code for user authentication and management and means we don't have to revinvent the wheel. Styling will need to be done for the necessary pages and there are likely to be bits of generated code that can be deleted. This will act as a starting point to be built up from using TDD.
3 years ago
errors:
messages:
Confirmable (#580) * Confirmable * Remove obsolete rake task * Skip confirmation for inactive users * Send beta onboarding template if migrated from Softwire * Default controller * Use correct link * Redirect confirmation to set password * Confirm account within 3 days * Only redirect to set password if not previously set * Rubocop * Confirm factory bot users * Set password condition * Changing email requires reconfirming * No need to explicitly trigger email, devise does that for us now * Remove flash banner * Mock notify * Mock in the right spec * Test redirect and text * User is confirmable * Rubocop * Redirect to url so we don't bypass authenticity token * Update content * Add test for resend invite flow * Update link to resend confirmation email * Rename password reset resend confirmation partial * Expired link error page * Remove resend confirmation link * Update seed * Expory contact * Time zone Co-authored-by: Paul Robert Lloyd <me+git@paulrobertlloyd.com>
2 years ago
already_confirmed: "Email has already been confirmed. Sign in."
Fix repeated use of Password in error summary (and use smart quotes)
3 years ago
blank: "can’t be blank"
Confirmable (#580) * Confirmable * Remove obsolete rake task * Skip confirmation for inactive users * Send beta onboarding template if migrated from Softwire * Default controller * Use correct link * Redirect confirmation to set password * Confirm account within 3 days * Only redirect to set password if not previously set * Rubocop * Confirm factory bot users * Set password condition * Changing email requires reconfirming * No need to explicitly trigger email, devise does that for us now * Remove flash banner * Mock notify * Mock in the right spec * Test redirect and text * User is confirmable * Rubocop * Redirect to url so we don't bypass authenticity token * Update content * Add test for resend invite flow * Update link to resend confirmation email * Rename password reset resend confirmation partial * Expired link error page * Remove resend confirmation link * Update seed * Expory contact * Time zone Co-authored-by: Paul Robert Lloyd <me+git@paulrobertlloyd.com>
2 years ago
confirmation: "Password confirmation doesn’t match new password"
confirmation_period_expired: "Email needs to be confirmed within %{period}. Request a new link below."
Update config/locales/devise.en.yml Co-authored-by: Paul Robert Lloyd <paulrobertlloyd@users.noreply.github.com>
3 years ago
expired: "Token has expired. Request a new token."
Update devise translation strings (#461)
3 years ago
not_found: "was not found"
not_locked: "has not been locked"
Add devise gem and a first test for user login Devise is a commonly used gem for user authentication and management. Using rails generators and Devise allows us to get a lot of boilerplate code for user authentication and management and means we don't have to revinvent the wheel. Styling will need to be done for the necessary pages and there are likely to be bits of generated code that can be deleted. This will act as a starting point to be built up from using TDD.
3 years ago
not_saved:
Update devise translation strings (#461)
3 years ago
one: "One error stopped this %{resource} from being saved:"
other: "%{count} errors stopped this %{resource} from being saved:"