Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Help users who accidentally include file extensions in urls
See original GitHub issueToday I was helping a user through some bugs in their prototype. One of the issues I observed is that they’d included file extensions in their urls and in their GET, POSTs, routes and renders.
Nominally the kit doesn’t need this, and I think it can lead to some unexpected behaviour. However for the most part things still appear to work.
If a user comes from a static html prototyping background there’s a good chance they might think they need extensions.
I wonder if there’s anything we could do to help with this?
Perhaps have the kit log a warning to the console when it gets a get request with an extension?
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@trang-erskine This is an issue I used to see frequently when running Prototype Kit training with @joelanman - it’s a logical thing to do when you want to link to a file - and especially if users have prior experience with html there’s a good chance they might do this.
theoretically that should just redirect to the same path without .html and still work, but worth reviewing