Closed webbpinner closed 7 years ago
Not sure what you mean. Can you screenshot what's wrong on the demo site (http://lout.herokuapp.com/docs?server=http://lout.herokuapp.com&path=/withcorstrue#GET) ?
My bad, should have done that in the first place. Original:
Modified:
I'm suggesting there may be an issue when auth is required and CORS is true.
Looks better indeed, I'm probably lacking a route test case for auth + CORS. Do you mind taking a stab at a patch ?
Just created a pull request. There appears to be some sort of auto-build process that is indicating build errors although they do not cite errors in the route.html file. Is there anything I need to do to make this pull request compatible with the master branch?
I will, it's been an outstanding issue for a while now, I need to fix it, but I'll have to require latest versions of everything in the process, hope that's ok with you.
I just integrated lout within my hapi project and had an issue with the route view. The CORS section starting on the last line of the auth section. Looking at the code it appeared that the auth section was using
<p>/<h4>
for the individual rows vs the rest of the template which was using<dl>
,<dt><dd>
. I converted the auth section of the template to use the<dl>
,<dt><dd>
and normalized some indentation discrepancies. That didn't fix the problem but it did make the resulting code more consistent. What ultimately did fix the problem was adding a<br/>
just before the closing{{/if}}
for the auth section.Thought I'd share in case this was in fact a bug.
Cheers, -W
Below is my replacement for the existing auth section in the routes template: