One of my mutuals on here bought a FIIO Snowsky Echo MP3 Player (the one which looks like a high end 90s Walkman) a while back... if you see this & it was you ... please let me know if you've been pleased with it 😅
I really want one & just need someone to enable me a bit...
![Why it is an Even Bigger issue in Multiplatform Projects
I work almost exclusively on multiplatform games, so the code I work with contains a large amount of #if PLATFORM_X ... #elif PLATFORM_Y ... #endif type code.
In a multiplatform codebase, the issue of builds breaking across multiple platforms because of a using added by auto-complete is even more prevalent.
I would estimate that 3/4 of all failed builds for the build machines building console versions of our game were caused by this single issue.
Why the existing autocomplete options in Rider do not fix this
When other people have raised this issue (many, many times) in the past they are usually told to use one of three existing Rider features which I have been told "will fix this":
1. Disable the checkbox Settings -> Editor -> General -> Code Completion -> [ ] Show Import Items in basic completion.
In fairness, this does prevent the issue, as autocomplete now won't insert suggest autocompletions which require a using statement.
However, having autocomplete suggestions only from existing imports drastically reduces the usefulness of autocomplete. You might as well suggest people google for the type name.
2. Use Settings -> Editor -> Code Cleanup -> Optimise imports ... to clean out the incorrect using xxx; statements.
This does not fix the issue at all!
Rider doesn't take into account conditionally compiled code which is not active when optimising imports and will consequently remove using statements which are necessary for some platforms and not for others
3. Use the filtering options in Settings -> Editor -> General -> Auto Import to control which assemblies are considered for code completion.
This also doesn't fix the issue - the issue here isn't that some assemblies should be ignored for code completion, it is that inserting a using directive is not always the best option.](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:xkctp2vphhhymiadea3gbqir/bafkreigzadgvyyvoa23qazmgnw6fs7ddg7pu5o27ftwnlweff4yikkfmpm)
![Possible fixes for the issue
These are all suggestions for additional Code Completion settings options.
A) "[ x ] hold <key> when accepting autocomplete to insert fully qualified type name"
Allow the user to choose whether to autocomplete by adding a using statement or by adding the fully qualified type name when autocompleting.
This is my "minimum viable solution" as it doesn't require the auto-complete code to take conditional compilation into account, and will still be very much prone to cause the same issue by human error.
B) "[ x ] always insert fully qualified type names in conditionally compiled code"
If the code being auto-completed code is withing a #if PREPROCESSOR_SYMBOL .... #endif then it will always use fully qualified type names for the autocompletion and never insert a using statement.
Does exactly what it says on the tin, I can't think of a way this could fail to address the issue.
C) "[ x ] if code is conditionally compiled, add imports with the same conditional compilation constraints"
I'm 95% sure this would work, but it will definitely be more complex and edge-casey than option A or B.
With this option, if autocompleted code is within a #if PREPROCESSOR_SYMBOL .... #endif then the using statement would be added with the same conditional compilation constraint . e.g.
using Some.Namespace.Or.Other;
#if PREPROCESSOR_SYMBOL
using Inserted.Namespace;
#endif](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:xkctp2vphhhymiadea3gbqir/bafkreih6cw6ybcxp4uieorbmz4q4qjqtogrj5py3gze2xslx7xnsxw2jwy)
![Solution: with the animation pane active in 'curves' view press [ctrl+a] then [f] to fit the zoom to the curves.](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:xkctp2vphhhymiadea3gbqir/bafkreie7rcgbc2dx4z4ipo4mrxut3txgjfo32mkh6niazohpeuo7gpnmcq)
