I'm not sure that I follow. IC has had support for LWC since that feature was in early beta. Note that if you're using IC with a free Community Edition IDE without first-class support for JavaScript and CSS, editor features have been limited, but that should be addressed next week. See the "Next in the work queue..." portion of the release notes from today's update: illuminatedcloud.blogspot.com/2024/11/2338-release-notes.html

In the browser view, do you see the local development server header displayed clearly? If not, make sure the feature is enabled in that org and for that user.

@@Illuminatedcloud Yeah i see clearly, but nothing change ! I don't know who contact for resolve this problem

@@moyaarnaud8877 Feel free to log an issue in the public issue tracker: bitbucket.org/RoseSilverSoftware/illuminatedcloud/issues That way you can attach screenshots and, if needed, logs. Assuming the local dev server is started and local dev is enabled in the org, it should just work. The IC integration is largely just helping you start/stop/restart the server with the correct arguments. Log an issue and I'll be happy to help troubleshoot...

I noticed that on a new project today as well. I believe at one point it would just open for the org, but now I think the behavior when you don't specify an app name is to prompt you the first time and that becomes the default app if unspecified on subsequent invocations. Just hit Enter and it'll move along, though it may not open the desired/expected app. I'm going to do something to avoid that command-line prompt and either have IC prompt or similar.

@@Illuminatedcloud Thanks for the quick reply. Look forward to an update on this

@@mikewiley977 And again, it's not keeping you from using the feature. Just hit Enter at that prompt and the org will open on the first listed application. From there you can open any app you want just as if it opened for the org.

@@Illuminatedcloud I see you fixed this in your latest version. I'd like to see an additional option to select the connection.

@@mikewiley977 When you start a run configuration using the context menu or context actions, the connection is derived concretely from the selection. If you'd like to specify the connection, you can create an explicit Local Development Server run configuration and select the connection and (optionally) the app or site.

Do you mean that it doesn't generate code that uses the shared libraries or that it's actually breaking in some fashion? Assuming you mean it's not taking into account your shared libraries, that's expected. The context that's currently provided in the prompt is quite limited, and the LLM really only has the provided context as insight into your project/org at the moment. There's already an enhancement request to be able to provide additional context with the requests: bitbucket.org/RoseSilverSoftware/illuminatedcloud/issues/2647 and in the future, Salesforce plans to make the LLM automatically aware of the respective org's contents without the API client having to include it as context in the request. If, on the other hand, you're seeing a bug, please file a bug in the public issue tracker.

@@Illuminatedcloud no bug, but no org specific awareness of things built before. I

@@vanbeukeringfamily1724 got it. Yeah, that's as-expected right now. I'll probably look into opportunities for context improvement a bit once I get the Winter '25 updates out, but the longer-term answer is that Salesforce is supposed to be adding full RAG support (effectively full knowledge by the model of the org's contents) at some point. Until then, the model only knows what it's been trained on and what you tell it in a given prompt.

Hi. I'm not sure what you're seeing (or in this case, not seeing). Can you please reach out via one of the support channels (www.illuminatedcloud.com/support) with more details on what you're seeing vs. what you're expecting?

@@Illuminatedcloud UPD=) I updated Idea and plugin 3 times today (every time was new version upgrade) and finally I reached the final version, and now it works=)

​@@anpos hmmmm...I'm glad to hear it works for you now, but I wouldn't expect more than two updates, one for the base JetBrains IDE and then one for the plugin itself, though I guess if you updated the plugin in an older IDE version, it would only update to the last plugin version that supported that IDE, then if you updated the IDE to the latest, the plugin could be updated to the latest-and-greatest. I guess that might make sense. Anyway, again, glad to hear that you're good to go now.

Hi. You should just need to download a PMD distribution (pmd.github.io/#downloads). I recommend 6.55.0 as it's the latest official released version. Extract that archive somewhere on your machine and register its root directory with the PMD Salesforce code inspection. Then create a ruleset file (raw.githubusercontent.com/pmd/pmd/master/pmd-apex/src/main/resources/rulesets/apex/quickstart.xml) and register that with the inspection as well. If you want to use the PMD AppExchange rules, install the Saleforce Code Analyzer CLI plugin (forcedotcom.github.io/sfdx-scanner/en/v3.x/getting-started/install/) and enable that inspection option. That should do it. If you're still having issues, please contact me via any of the support channels (www.illuminatedcloud.com/support).

Yes, as an open beta starting last week with the kickoff of Dreamforce 2023: developer.salesforce.com/blogs/2023/08/einstein-for-developers-open-beta

Thank you!

Yes, you must have the Functions feature enabled in an org in order for your functions to be able to deploy them into a compute environment and invoke them from your Salesforce org. You can play with functions locally without that, though, e.g., create run them locally including running queries and performing DML against your org from functions. I cannot comment on how/why Salesforce licenses this the way that they do unfortunately.

@@kiadel7502 If you mean that they're showing up as unresolvable, yes, there's a regression introduced in a recent JetBrains IDE update. The next build (final testing now) has a fix for that.

@@Illuminatedcloud 13:25 Apparently I can modify only once, subsequently changes aren't saved. Using "build project". If I do this "SELECT Id, Name, LastModifiedDate, AccountNumber ..." it won't work.

@@kiadel7502 That's correct. No hot deploy. The function is running in a local "container" managed by the 'sf' CLI. You must restart it from the Salesforce Functions Dashboard.

@@Illuminatedcloud I tried that, AccountNumber is not recognized. I can play with Id, Name, LastModifiedDate, as in you video. But when it comes down to play with other fields don't work. Apparently. For example if I do this : "SELECT Id, Name, AccountNumber, AnnualRevenue FROM Account" it gives me back only Id and Name.

Well like I said in the demo and release notes, Chris Baker gets full credit for recommending that as an improvement to the more simplistic "sd" variant.

I would highly recommend adding the non-user-specific portions of .idea to version control. It's actually designed (by JetBrains) for that to provide consistency in a team environment: www.illuminatedcloud.com/support/faq#h.xgckaanqlbu2 Totally fine if you don't, but I would take a minute to review both the linked item above and the JetBrains page linked from that on the topic.

Smart completion is SUCH a time-saver. To be fair, though, until 2.2.3.6 it added more overhead in some situations in Apex as to marginalize its usefulness. Hopefully with the optimizations added in 2.2.3.6 and enhancements added in 2.2.3.7 atop that, it can/will become a more standard part of IC2 users' daily workflows.

Hi, Mark. This isn't part of a public/shared repo. It comes from one of several smoke test projects that I use for both testing and demos. Is there some specific aspect of it that you'd like to access so that you can play around with the features?

@@Illuminatedcloud Hi Scott, many thanks for your reply. Yes, just want to test it out the features with hands on by using the same file from your demo. It's no biggie if it's not convenient to share :)

@@markdu2682 I'm sure there's a subset of the test harness that I could share with you. Please reach out via [email protected] and let me know specifically which files you were interested in having.

In the drop-down menu, check View > Appearance > Toolbar. Let me know if that doesn't get you there.

@@Illuminatedcloud it did, perfect! Thanks

Thanks for the info. The Tooling API SObjects are discovered using the Tooling API itself, so if they're missing it's due to an omission in the Tooling API's response. IC2 has a provision for filling in such gaps, though, as they're not terribly uncommon in the Tooling API. If you don't mind, please file a bug in the IC public issue tracker with whatever details you can provide and I'll be happy to take care of it.

I decided to take a quick look at this today and find the cited objects--PlatformEventChannel, PlatformEventChannelMember, and PlatformEventSubscriberConfig--properly generated into the OST under the ToolingApi namespace and available for SOQL query authoring and executing. I did, however, find a number of documented Tooling API SObjects that are not reported by the Tooling API and are therefore not included in a generated OST. I'm going to see whether those are a doc issue or an API issue and, if the latter, will add them explicitly to the OST so they're available for queries. If you're not seeing the original objects that you mentioned in your generated OST, though, please let me know as that would represent a pretty significant omission relative to what I'm seeing across numerous orgs.

Do you mean in terms of query execution or deployment? If the former, I haven't really seen a difference in query execution times, though with only a subset of common objects with common fields, most queries aren't going to be apples-to-apples. If you mean the latter, though, yes, the Tooling API was obviously purpose-built for IDE-type use cases with frequent, small payload deployments like you'd have with deploy-on-save behavior.

Hi, Stephen. The purpose of that specific feature is to allow you to work against scratch orgs as if they were not source-tracked scratch orgs. This is very useful for those that haven't yet moved to a full SFDX scratch org model and those who never plan to do so...those that prefer explicit metadata deployment/retrieval/removal to source tracking. You get the benefits of scratch org rapid and programmatic provisioning while supporting development processes (interactive and scripted) that aren't based on source tracking. Of course, if you're working against a scratch org using source tracking (i.e., push and pull), you don't need a package.xml file as the source tracking metadata will take care of synchronizing local vs. org metadata when those actions are performed. IC2 supports pretty much all possible Salesforce development models in terms of on-disk format (metadata format vs. source format); org types (DE/sandbox/production orgs vs. scratch orgs); and metadata management types (explicit deploy/retrieve/remove vs. source tracking). Let me know if that doesn't clear it up for you.

@@Illuminatedcloud Sorry, I should have been more specific. My org is doing package based development. we have a single sandbox org, but all of our development is against scratch orgs. We do not utilize a package.xml manifest file for this project. Is it possible to use your plugin without this?

should my connection for the project be against my `global connection` rather than the scratch org?

@@z1haze Yes, absolutely. The user guide (bitbucket.org/RoseSilverSoftware/illuminatedcloud/wiki/User_Guide/Home) includes several topics on the various ways that projects can be created including from version control, from existing files, from an existing org, etc. You'd basically create a new SFDX project as appropriate and then either create a new scratch org in support of that project or select an existing scratch org if you already have one. If you don't check "Generate manifest" there will be no package.xml file and, if you're working against a scratch org, IC2 will automatically use push and pull to move metadata back and forth. Feel free to reach out via [email protected] with specific questions and I'll be happy to help you get a project set up based on your team's development model.

My apologies. Upon configuring an org connection and accepting/okaying out of the project structure dialog it offered to generate it for me.

@@ianutube22 regarding your original question, though, yes, IC2 does currently require a package.xml-based metadata subscription for source format projects against non-scratch (or at least non-source-tracked) orgs. It's perhaps an artificial requirement as IC2 will actually maintain a dynamic subscription for source-tracked projects where the real "subscription" is maintained by the CLI's/org's source-tracking metadata. It wouldn't likely be difficult to remove that artificial requirement so that projects like yours do the same thing if no physical subscription is specified. If that's something you'd like to see so that you don't have to have a package.xml file for this project that's shared with your teammates, feel free to log an enhancement request in the public issue tracker (bitbucket.org/RoseSilverSoftware/illuminatedcloud/issues?status=new&status=open) and I'll be happy to take a look.

At this point the Salesforce Functions beta cycle is completed, and the feature won't be available until Winter '22 has been released. I'll include these features in the Winter '22 IC2 update in a few weeks.

@@Illuminatedcloud ok. Thanks.

@@Illuminatedcloud Oh this is new to me...is this published and official? I'm officially sad :-D this feature has been delayed for ages...

@@attilah the underlying Salesforce feature will be released in a few weeks as part of Winter '22. I'll include the IC2 features shown in this demo as part of the IC2 Winter '22 update.

@@Illuminatedcloud Ah sorry, I meant Salesforce Functions, not the IC2 Functions support ;-) You are doing awesome stuff Scott! One feature suggestion would be to have a folder in the project structure where payloads could be persisted and selected from a dropdown when manually invoking the function from the IDE, that would be a huge help.

It's getting very close. The only thing left to implement is managed/monitored deployment to Heroku, and of course some second-pass clean-up/refinement. But function creation, authoring, local deployment/debugging in Docker, etc., are all in very good shape. I hope to have a test build out next week at latest.

@@Illuminatedcloud Any updates on then new build Scott with "Functions"? Any beta build or something which can be tagged to my license key so that I can try that from my end to check the functionality.

@@NagendraSingh-vm1yd I'm hoping to post a build this week. The only two things left to implement are local execution of functions against a locally-deployed container and code completion/reference navigation for string literal references to function names in Apex. But function creation, removal, local deployment to Docker, remote deployment to Heroku, etc., are all implemented and working really well. Oh, and before I post the build I plan to record a pretty comprehensive HOWTO video demonstrating all of these features and how they're used. So, soon...hopefully this week, but potentially next week.

You know, there's a plugin that actually shows the keyboard shortcuts as you use them, and for a while I had that enabled when I'd record demos. I'll make sure I'm doing that consistently going forward. I think it just slipped my mind on this one. Are there particular actions in this demo for which you'd like to know the keyboard shortcuts? I'm happy to identify them here for now since I didn't have that plugin enabled.

@@Illuminatedcloud How you get the anonymous execution? Can you do a video how we can you the interactive debugger

​@@Lankathilaka the keyboard shortcuts are covered here: www.illuminatedcloud.com/support/faq. If you specifically mean how to execute an anonymous Apex script (or SOQL query), it's Ctrl+Enter (Windows/Linux) or Cmd+Enter (Mac). Note that in most cases if you want to know the keyboard shortcut for an action that is also available as toolbar button, you can hover the mouse over that button and it will show the action name, description (sometimes in the status bar), and keyboard shortcut. There is currently no support for the live/interactive debugger. Here are videos for the offline/log-based debugger: kzbin.info/www/bejne/bZnIoKmVZb6XbKc kzbin.info/www/bejne/r6LWoISFa9hgiqM

It's the little things, eh?

@@Illuminatedcloud Yep sometimes it is, had meant to message about if that could be stopped somehow ;) Also love the new option for the Anonymous Execute, that has been annoying at times too, especially if you have a chunk of code commented out but want it for now... So thanks for pointing these out, passed them on to the team to get hopefully spread the knowledge :)

Leo, I'm sorry that you're not happy with the product. I'm happy to answer any questions for which you can't find an answer. The best contact channels would be the public issue tracker, the public discussion groups, or the support email alias. Because Illuminated Cloud builds upon the JetBrains IDE, often their documentation already provides details on how to do shared actions, e.g., file creation. You can create any type of new file using the same steps documented at: www.jetbrains.com/help/idea/add-items-to-project.html As long as you're starting from a source root, it should present the file types for creation that are valid under the selected directory, e.g., Apex classes under "classes", LWC bundles under "lwc", etc. Feel free to reach out via any of the aforementioned channels if this doesn't help and/or if you have other questions about how to use the product.

I apologize but I'm not sure I follow the question. Are you asking how those stub Apex classes are generated?

@@Illuminatedcloud Yes. The Apex ones provided by the SF runtime, like System, Actor, JSON, JSONGenerator etc. Not the SObjects and Custom Objects that are queryable through SOAP. Still catching up on the videos, but you got yourself a customer :-D Awesome job you are doing with this product, I wish it would exist for VS Code ;-)

@@attilah well, the core definitions are queried using the Tooling API's completions resource (developer.salesforce.com/docs/atlas.en-us.api_tooling.meta/api_tooling/intro_rest_resources.htm). However, that returns a VERY rough (incomplete and incorrect) representation of the Salesforce system Apex types, and Illuminated Cloud's offline symbol table generator enriches it extensively to provide a high-fidelity version of the actual system types.

@@Illuminatedcloud Ah makes sense, thanks. Too bad it is not common knowledge and SF does not provide all the goodies. The reason I was asking is that I came across apexsharp (github.com/apexsharp/apexsharp) which is kinda abandoned and was looking for a way to refresh those classes to get it up to date.

@@attilah You might reach out to Jay (the developer of ApexSharp) directly. He's a great guy and can likely give you thoughts on how he'd go about updating them. If you're not sure how to contact him, feel free to ping me directly via email and I can connect the two of you.