I wonder if there isn't some sort of validation or coercion we could do without narrowing the use cases. As far as I can tell, the protocol (http, https, etc) is required or it becomes a relative link. For example:
- 'https://www.example.com' -> 'https://www.example.com' - 'www.example.com' -> 'localhost:8000/www.example.com' - 'example.com' -> 'localhost:8000/example.com' These are all ways people are used to using urls, even if they're technically incomplete. I think they can also all be parsed in such a way that they're unambiguously external. On Sunday, July 5, 2015 at 8:28:50 PM UTC-4, Stephen McDonald wrote: > > Hi all, > > We're looking at fixing some issues around the Link model. Its original > intention was for external links (to other websites), but people currently > use it with internal links as well to achieve different scenarios with site > navigation. If you have other examples of this that you depend on, could > you chime in here: > https://github.com/stephenmcd/mezzanine/issues/1345#issuecomment-118676898 > > Thanks > > > -- > Stephen McDonald > http://jupo.org > -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
