-
Notifications
You must be signed in to change notification settings - Fork 162
Fixed template override lookup for support ticket API content #4844
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
base: master
Are you sure you want to change the base?
Conversation
adebe2f to
a68afbb
Compare
|
Sorry for the delay, I'll get to this shortly. |
Still need to carve out time and refresh my memory on this. These do not appear to be ActiveModels, but my first instinct is to mention implementing |
|
Not sure I follow, but the main problem is the lookup of the template given a template path. |
Rails docs appear to be down, but you can call
as these objects do ondemand/apps/dashboard/app/models/motd_formatter/osc.rb Lines 30 to 32 in 7c96d05
But again, I don't know if that fits here as these are using views, but do are not actually rendering HTML for a page through a controller. |
|
This render helper method available in the Rails template rendering context. It is the equivalent (if not the same) as As these are service classes that are not part of the rendering process, using the template based approach does not work. This is why I am rendering the template this way. I added the templates into the views folder to make it easier to locate and understand when looking at the code, but they are not use to render an HTML page in the application. They are used to generate the main content for the support ticket system API request payload. |
Fixes to the Request Tracker and ServiceNow backend implementation for Support Ticket functionality.
The fixes are for the template lookup to that is used to generate the content with the job/session info and sent to the remote system. Now it is using Rails lookup respecting views locations and overrides for the template lookup.
Before it was using only the view folder under the main Rails.root directory