Title: Enable IntelliSense based purely on version-specific PowerShell metadata · Issue #308 · PowerShell/PowerShellEditorServices · GitHub
Open Graph Title: Enable IntelliSense based purely on version-specific PowerShell metadata · Issue #308 · PowerShell/PowerShellEditorServices
X Title: Enable IntelliSense based purely on version-specific PowerShell metadata · Issue #308 · PowerShell/PowerShellEditorServices
Description: A fairly common request is for the editor to give IntelliSense for a particular version of PowerShell. For instance, a user on a Windows 10 machine with PowerShell 5.1 might want to emulate IntelliSense for a Windows 7 machine running Po...
Open Graph Description: A fairly common request is for the editor to give IntelliSense for a particular version of PowerShell. For instance, a user on a Windows 10 machine with PowerShell 5.1 might want to emulate Intelli...
X Description: A fairly common request is for the editor to give IntelliSense for a particular version of PowerShell. For instance, a user on a Windows 10 machine with PowerShell 5.1 might want to emulate Intelli...
Opengraph URL: https://github.com/PowerShell/PowerShellEditorServices/issues/308
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Enable IntelliSense based purely on version-specific PowerShell metadata","articleBody":"A fairly common request is for the editor to give IntelliSense for a particular version of PowerShell. For instance, a user on a Windows 10 machine with PowerShell 5.1 might want to emulate IntelliSense for a Windows 7 machine running PowerShell 2.0. It'd be nice if we could switch to a compatibility mode which provides cmdlet and .NET IntelliSense based on what's available on the target platform. This would also be helpful for those writing scripts using PSES on Linux and macOS since PowerShell v6 has a different cmdlet/featureset than any of the Windows PowerShell versions.\r\n\r\nOne other benefit of this feature is that it could allow us to do IntelliSense without an active runspace. This would be helpful in cloud based-editing scenarios because a hosted PSES service could give IntelliSense without the need for a running PowerShell session.\r\n\r\nWe should figure out how to integrate this into PSES before 1.0 just in case it requires any design changes. If we can implement this without changing any APIs then we could potentially push the implementation past 1.0.\r\n\r\n/cc @kapilmb ","author":{"url":"https://github.com/daviwil","@type":"Person","name":"daviwil"},"datePublished":"2016-12-05T15:21:46Z","url":"https://github.com/PowerShell/PowerShellEditorServices/issues/308"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322 |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:3237ae74-448e-7961-e7ad-958a7653d255 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | 984E:3C18DC:10FF76:18502A:6AFD4D40 |
| html-safe-nonce | 3c15f04f3c619e16e5e86c31dc6e343ee89ba0e69fa5592449969d78bdadd2a4 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiI5ODRFOjNDMThEQzoxMEZGNzY6MTg1MDJBOjZBRkQ0RDQwIiwidmlzaXRvcl9pZCI6IjY0ODI1MDE3ODk2ODMwOTA1NiIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | 1e6ecb02c27f5ce139f42e8d66bd0d4aab70765fe8501b259eceb98e2bc56aa7 |
| hovercard-subject-tag | issue:193526137 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/PowerShell/PowerShellEditorServices/308/issue_layout |
| twitter:image | https://opengraph.githubassets.com/acc63e30c439b629477038975143d145a70159a58b6004752fd58aa0790a68f3/PowerShell/PowerShellEditorServices/issues/308 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/acc63e30c439b629477038975143d145a70159a58b6004752fd58aa0790a68f3/PowerShell/PowerShellEditorServices/issues/308 |
| og:image:alt | A fairly common request is for the editor to give IntelliSense for a particular version of PowerShell. For instance, a user on a Windows 10 machine with PowerShell 5.1 might want to emulate Intelli... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | daviwil |
| hostname | github.com |
| expected-hostname | github.com |
| None | 66653c2e55a6fff2930be1bdf07ee4f8aa137e3956d056c822563be6f878755e |
| turbo-cache-control | no-preview |
| go-import | github.com/PowerShell/PowerShellEditorServices git https://github.com/PowerShell/PowerShellEditorServices.git |
| octolytics-dimension-user_id | 11524380 |
| octolytics-dimension-user_login | PowerShell |
| octolytics-dimension-repository_id | 36031537 |
| octolytics-dimension-repository_nwo | PowerShell/PowerShellEditorServices |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 36031537 |
| octolytics-dimension-repository_network_root_nwo | PowerShell/PowerShellEditorServices |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | b6f01f7cb9f35f8c09949773241a3d49dd04b340 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width