Feedback
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- developer-experience, tooling
Research direction
Issue 210 is general feedback from a Salesforce Developer about Code Builder, including a request for better refactoring options. It names no files, tests, or entry points and provides no concrete acceptance criteria, so the scope and definition of done would need to be established before implementation.
Written by the indexing model from the issue text.
Description
What is your role?
Salesforce Developer
What do you normally work on when building on the Salesforce Platform?
Frontend, Backend, Integrations and more
What tools do you use today to develop on the Salesforce Platform?
Mainly IntelliJ with IlluminatedCloud and VS Code with the Extension Pack
How do you see Code Builder fitting into your current workflow? Will it replace any tools you are currently using?
It will definitely replace my current setup for orgs where it doesn't make sense to create the whole project just for minor edits. If the experience remains as good as now, it will definitely be my main daily driver.
General feedback
I'm really glad that there is finally a viable alternative for the Developer Console. In terms of some minor improvements, I'd love to see better refactoring options (as seen in IntelliJ).
- Dominant language
- No language data
- Stars
- 35
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from forcedotcom/code-builder-feedback
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
forcedotcom/code-builder-feedback#273 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
forcedotcom/code-builder-feedback#265 · 2 comments ·
-
type:enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
forcedotcom/code-builder-feedback#262 · 1 comment ·
All issues in forcedotcom/code-builder-feedback
Similar issues
-
Difficulty 2/5 Half a day Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 1/5 Under an hour Newbie friendliness 90/100
JustJarethB/invoicer#54 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
comp/tools P3 type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
NousResearch/hermes-agent#126059 ·
Maintainers usually reply within 1 day