I sometimes wish to add a link to a devzone discussion in a code comment where the topic is relevant. For example, https://devzone.nordicsemi.com/f/nordic-q-a/43316/nrf52832-saadc-configuration-effects-on-calibration provides information on conditions for calibrating the SAADC peripheral.
It appears I have to provide that entire link, including the tokenized post subject, to retrieve the discussion. Using only https://devzone.nordicsemi.com/f/nordic-q-a/43316/, which really ought to be unique, gets nowhere.
It would be nice if the shorter form worked.
Hey pabigot, interesting point. IMO I'd be hard pressed to call it critical, but I'll look into it :)Cheers;Eivind
Did it get ranked as critical somehow? Wasn't my intent.
No, it's not critical. I remember having to go back and update about a dozen links in my header files when y'all switched to the "new" devzone around December 2017. At that time what had been https://devzone.nordicsemi.com/question/46716 had to change to https://devzone.nordicsemi.com/f/nordic-q-a/8458/hfclkstart-blocks-changes-to-lfclksrc/, which is when I first noticed the requirement to include the subject text.
Hehe, no it was ranked in anyway - just my remark to say that I personally dont find this a big problem :) The serious part there, which I realized after your 2nd post - is that your ticket should have had a redirect installed back when it was migrated from the old devzone. I'm not sure why this did not happen, so we'll just have to look into it. Sorry for that inconvenience!
Regarding the subject text in strings etc: That's apparently just how routing in telligent works. The url has to have something after the post id. But it doesn't have to be meaningful - and doesnt have to be the subject text.
can be also presented as
you can replace the word "anything" with literally anything - even just a single letter.So in your case, for example: https://devzone.nordicsemi.com/f/nordic-q-a/43316/ror https://devzone.nordicsemi.com/f/nordic-q-a/43316/saadc
Sounds like telligent isn't very intelligent.... Thanks for the tip. If that part of the path works with any non-empty text that's probably good enough.
In my case no need to do anything about the missed forwarding from the old devzone; I've already updated everything. It was a bit annoying at the time, but I'm mostly over it now ;-).
Thanks pabigot, gotta check it out anyway. Have not seen more missing redirects so have to dig into it.