Quick questions

[Rodrigo Zurek]

Hey Scott

I just started using IC, I come from another competitor that went stale and stopped providing updates. 

Here are a couple of things that I miss from the other plugin and maybe it is possible in IC (maybe I'm dumb and don't know how to configure 😅) 

1. When a file is modified and not yet deployed the other plugin made a highlight color for the file. sometimes I modify a couple of files and instead of doing a full metadata deploy I just want to deploy the changes but the IDE does not mark the ones I changed.

If I'm not mistaken I think the other plugin compared the time the file was modified vs the time of last successful deployment.

2. debug log error filter, just like the Debug Only filter the other plugin had a checkbox to only show exceptions and also showed them highlighted in red.

3. deploy metadata to another org not configured in the current project. The other plugin had a "deploy to another org" option where you selected the connection and it tried to deploy the metadata file to another org with the selected connection.

Those are my current issues on my first week of testing. 

Please let me know if this is valuable or if I'm just a nuisance  😅

Thanks!
Rod

[Scott]

Hi, Rod. I don't ever mind questions, so please don't hesitate to ask whatever you'd like. I definitely want to make sure that users are getting the most out of IC, and that includes both educating them about existign features and fielding suggestions for improvement.

Regarding deployment of only modified files, there are two core features.

The first is the Deploy Modified Metadata action. It doesn't visually highlight the changed metadata in the Project view or editor tabs so as to defer potentially expensive local-vs-server timestamp comparison to the time of deployment, but it does compare those timestamps when a deployment is requested and only includes out-of-date files in the deployment payload.

The second is a pretty recent feature where you can change the Contents drop-down of the bulk metadata deployment(/retrieval/removal dialog to any IDE-defined scope including VCS-based scopes such as All Changed Files (Local Changes). If your project is configured against VCS, that will allow you to ensure that all modified files are included in the deployment payload. It can also be used with Deploy Modified Metadata if you'd like both dirty-relative-to-VCS and dirty-relative-to-org to be considered, or it can be used with Deploy All Metadata which will deploy everything that's changed relative to VCS even if it's already up-to-date in the org.

Regarding a filter for errors, there's currently no such explicit feature. If you'd like to see one, feel free to log an enhancement request in the public issue tracker. However, IC does hyperlink Apex stack traces in debug logs, and you can use the log viewer's Up/Down the Stack Trace actions to navigate to hyperlinked code coordinates in any open log.

Regarding deployment to another org, that's supported in the same bulk metadata deployment(/retrieval/removal) dialog. Just use the Connection drop-down to choose any configured connection that's compatible with the current project -- specifically native connections are not compatible with source format projects -- and the operation will occur against that org. The selected connection will also be added to the top of the connection list under Recent Connections if it's not a project connection so that you can use it again quickly and easily.

Let me know if that doesn't help, and don't hesitate to send over any other questions you might have.

Regards,

Scott Wells

[Rodrigo Zurek]

Hey Scott

Thanks for the quick reply ! 

Your answers pointed me to the right direction for everything. 

Created this quick video (attached) on how I manage to solve the highlighting issue in kind of a seamless way for me:


Thanks again, and il make sure to post any suggestions that come to mind
Rod

[Scott]

Hey, Rod. Glad that helped, and thanks for the demo video. That's great that you were able to put together some extended tooling that supports your preferred edit/VCS/deploy workflow! Thanks for sharing, and again, don't hesitate to let me know if you have other questions or issues.

Regards,

Scott Wells