-
Notifications
You must be signed in to change notification settings - Fork 9
[Docs] Add conventions documentation #4718
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
dd2d946
to
9717ef7
Compare
472f038
to
56b2d28
Compare
6acb1b7
to
36c209e
Compare
36c209e
to
24707cd
Compare
24707cd
to
fc8c0be
Compare
|
||
def t(key, options = {}) | ||
I18n.t(key, options.merge(scope: [:forms, *options[:scope]])) | ||
end |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we need to call in the view, is the idea to:
form.object.t('.something')
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No. This is for internally within the object itself. t
should be private
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor question: Courses::Query
might be in the API in the future so the namespace of Find
was not added. So what happens on these edge cases?
The PR looks good to me, 🚀
If there is no service namespace, it would be considered shared code :) |
fc8c0be
to
b658034
Compare
Context
We want to align on how the Publish Teacher Training code should be written.
Update: In order to turn this into a collaboratively iterative process, let's start here and add more content in separate PRs.
Changes proposed in this pull request
Guidance to review
View the documentation here: