Git Product home page Git Product logo

salesforce.nvim's Introduction

Hey, thanks for stopping by! ๐Ÿ‘‹ My name is Jonathan. I'm a professional software developer and am the founder of Forcecode.io, a site to help people learn the Apex programming language and get their dream job as a Salesforce developer. You can connect with me here:

Some tidbits:

  • ๐Ÿ‘ฏ Iโ€™m open to collaborate on projects of all kinds (if you're interested, please reach out!)
  • ๐Ÿ’ฌ Feel free to reach out to ask me about my work - please open an issue if related to one of my repos
  • ๐Ÿ“ซ How to reach me: Click the links above or email me at [email protected]
  • โšก Fun fact: I used to be a full-time musician and have a YouTube channel where I post my work!

Repos you might find interesting:

salesforce.nvim's People

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar

salesforce.nvim's Issues

Plenary error

Description

After adding the salesforce.nvim plugin to the lazy, a message appears every time I start nvim:

Failed to source `C:/Users/patry/AppData/Local/nvim-data/lazy/salesforce.nvim/plugin/salesforce.lua`

vim/_editor.lua:341: C:\Users\patry\AppData\Local\nvim\init.lua..nvim_exec2() called at C:\Users\patry\AppData\Local\nvim\init.lua:0..C:/Users/patry/AppData/Local/nvim-data/lazy/salesforce.nvim/plugin/salesforce.lua: Vim(source):E5113: Error while calling lua chunk: ...ta/Local/nvim-data/lazy/plenary.nvim/lua/plenary/job.lua:405: Failed to spawn process: {
  _additional_on_exit_callbacks = {},
  _shutdown_check = <userdata 1>,
  _stderr_results = {},
  _stdout_results = {},
  _user_on_exit = <function 1>,
  _user_on_stderr = <function 2>,
  args = { "org", "list", "--json" },
  command = "sf",
  enable_handlers = true,
  enable_recording = true,
  interactive = true,
  pid = "ENOENT: no such file or directory",
  stderr = <userdata 2>,
  stdin = <userdata 3>,
  stdout = <userdata 4>,
  user_data = {},
  <metatable> = <1>{
    __index = <table 1>,
    _create_uv_options = <function 3>,
    _execute = <function 4>,
    _pipes_are_closed = <function 5>,
    _prepare_pipes = <function 6>,
    _reset = <function 7>,
    _shutdown = <function 8>,
    _stop = <function 9>,
    add_on_exit_callback = <function 10>,
    after = <function 11>,
    after_failure = <function 12>,
    after_success = <function 13>,
    and_then = <function 14>,
    and_then_on_failure = <function 15>,
    and_then_on_failure_wrap = <function 16>,
    and_then_on_success = <function 17>,
    and_then_on_success_wrap = <function 18>,
    and_then_wrap = <function 19>,
    chain = <function 20>,
    chain_status = <function 21>,
    co_wait = <function 22>,
    is_job = <function 23>,
    is_running = <function 24>,
    join = <function 25>,
    new = <function 26>,
    pid = <function 27>,
    result = <function 28>,
    send = <function 29>,
    shutdown = <function 30>,
    start = <function 31>,
    stderr_result = <function 32>,
    sync = <function 33>,
    wait = <function 34>
  }
}
stack traceback:
^I...ta/Local/nvim-data/lazy/plenary.nvim/lua/plenary/job.lua:405: in function '_execute'
^I...ta/Local/nvim-data/lazy/plenary.nvim/lua/plenary/job.lua:448: in function 'start'
^I...data/lazy/salesforce.nvim/lua/salesforce/org_manager.lua:115: in function 'get_org_info'
^I...data/lazy/salesforce.nvim/lua/salesforce/org_manager.lua:22: in function 'new'
^I...data/lazy/salesforce.nvim/lua/salesforce/org_manager.lua:207: in main chunk
^I[C]: in function 'require'
^I...ata/lazy/salesforce.nvim/lua/salesforce/execute_anon.lua:3: in main chunk
^I[C]: in function 'require'
^I...cal/nvim-data/lazy/salesforce.nvim/plugin/salesforce.lua:1: in main chunk
^I[C]: in function 'nvim_exec2'
^Ivim/_editor.lua:341: in function 'cmd'
^I...
^I.../Local/nvim-data/lazy/lazy.nvim/lua/lazy/core/loader.lua:483: in function 'source'
^I.../Local/nvim-data/lazy/lazy.nvim/lua/lazy/core/loader.lua:442: in function 'source_runtime'
^I.../Local/nvim-data/lazy/lazy.nvim/lua/lazy/core/loader.lua:410: in function 'packadd'
^I.../Local/nvim-data/lazy/lazy.nvim/lua/lazy/core/loader.lua:345: in function '_load'
^I.../Local/nvim-data/lazy/lazy.nvim/lua/lazy/core/loader.lua:190: in function 'load'
^I.../Local/nvim-data/lazy/lazy.nvim/lua/lazy/core/loader.lua:122: in function 'startup'
^I...AppData\Local\nvim-data\lazy\lazy.nvim/lua/lazy/init.lua:110: in function 'setup'
^IC:\Users\patry\AppData\Local\nvim/lua/core/lazy.lua:14: in main chunk
^I[C]: in function 'require'
^IC:\Users\patry\AppData\Local\nvim\init.lua:2: in main chunk
stack traceback:
^I[C]: in function 'error'
^I...ta/Local/nvim-data/lazy/plenary.nvim/lua/plenary/job.lua:405: in function '_execute'
^I...ta/Local/nvim-data/lazy/plenary.nvim/lua/plenary/job.lua:448: in function 'start'
^I...data/lazy/salesforce.nvim/lua/salesforce/org_manager.lua:115: in function 'get_org_info'
^I...data/lazy/salesforce.nvim/lua/salesforce/org_manager.lua:22: in function 'new'
^I...data/lazy/salesforce.nvim/lua/salesforce/org_manager.lua:207: in main chunk
^I[C]: in function 'require'
^I...ata/lazy/salesforce.nvim/lua/salesforce/execute_anon.lua:3: in main chunk
^I[C]: in function 'require'
^I...cal/nvim-data/lazy/salesforce.nvim/plugin/salesforce.lua:1: in main chunk
^I[C]: in function 'nvim_exec2'
^I...
^I.../Local/nvim-data/lazy/lazy.nvim/lua/lazy/core/loader.lua:483: in function 'source'
^I.../Local/nvim-data/lazy/lazy.nvim/lua/lazy/core/loader.lua:442: in function 'source_runtime'
^I.../Local/nvim-data/lazy/lazy.nvim/lua/lazy/core/loader.lua:410: in function 'packadd'
^I.../Local/nvim-data/lazy/lazy.nvim/lua/lazy/core/loader.lua:345: in function '_load'
^I.../Local/nvim-data/lazy/lazy.nvim/lua/lazy/core/loader.lua:190: in function 'load'
^I.../Local/nvim-data/lazy/lazy.nvim/lua/lazy/core/loader.lua:122: in function 'startup'
^I...AppData\Local\nvim-data\lazy\lazy.nvim/lua/lazy/init.lua:110: in function 'setup'
^IC:\Users\patry\AppData\Local\nvim/lua/core/lazy.lua:14: in main chunk
^I[C]: in function 'require'
^IC:\Users\patry\AppData\Local\nvim\init.lua:2: in main chunk

# stacktrace:
  - vim\_editor.lua:341 _in_ **cmd**
  - ~\AppData\Local\nvim/lua/core/lazy.lua:14
  - ~\AppData\Local\nvim\init.lua:2

Steps to reproduce

  1. On a clean nvim configuration, I added lazy along with salesforce.nvim and its dependencies
  2. Error above appears

Environment

  • Neovim version: v0.9.5
  • LuaJIT version: 2.1.1703942320
  • salesforce.nvim version: latest
  • System: Windows 11
  • Shell: pwsh
  • Plugin clash: Plenary

Ignore conflicts when deploying

Describe the problem

There is a configuration option for file manager to ignore conflicts. This option adds --ignore-conflicts flag for sf project retrieve command. I would also like to have that same option for sf project deploy command.

Describe the solution

Option 1 would be to utilise the same configuration option and just add --ignore-conflicts flag to the deploy command in the same way as it is done for retrieve command.

Option 2 might be to change the setting and have a separate one for retrieval and deployment. Than use those settings when adding a flag to retrieve and deploy commands respectively.

LWC deployment error does not show

Description

When pushing an LWC and there is an error when deploying (e.g., when the file name does not match the parent directory name), the error is not easily visible in Neovim.

Steps to reproduce

  1. Create an LWC
  2. Rename the files but do not rename the parent directory
  3. Error message is unhelpful: Error(s) while pushing dropdown.js. Check diagnostics. Overlapping messages from apex_ls have been omitted.

Expected behavior

Error from command should show: No base file for markup://c:

Cannot select default org

Description

E5108: Error executing lua ...nvim/lazy/salesforce.nvim/lua/salesforce/org_manager.lua:128: attempt to concatenate local 'org_alias' (a nil value)
stack traceback:
...nvim/lazy/salesforce.nvim/lua/salesforce/org_manager.lua:128: in function 'select_org'
[string ":lua"]:1: in main chunk

Steps to reproduce

  1. I did SalesforceSetDefaultOrg
  2. image
  3. tried to hit enter on line 3
  4. Error

Expected behavior

Set the default org or give me a hint? I figure this has to do with the alias being nil but unsure

Environment

  • Neovim version: Nightly(10.x)
  • salesforce.nvim version: latest
  • Plugin clash: NA
  • Ubuntu 23.10

Compilation issues do not show in correct buffer after pushing when viewing a different buffer

Description

When a class file is pushed to an org and you switch to a different buffer, the diagnostics do not appear in the correct buffer.

Steps to reproduce

  1. Write a class that will not compile correctly
  2. Push it to the default org
  3. Immediately switch to a different buffer
  4. Diagnostics do not appear in the correct buffer

Expected behavior

Diagnostics appear in the correct buffer regardless of the currently open buffer.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.