0.0.3 (and later)

[tmkw]

At first glance, I feel the bellowings are candidates. Of course not all are covered in 0.0.3.

• rubygems trouble: homepage isn't displayed at rubygems.org. Maybe something should change gemspec.
• sf project deploy start
• sf project retrieve start
• sf project convert source
• sf org list
• sf org logout
• sf data create record
• sf data delete record
• sf data get record
• sf data update record
• sf apex run
• sf apex run test
• sf apex generate class
• sf apex generate trigger
• sf apex get test
• sf apex list log
• sf apex get log
• sf schema generate field
• sf schema generate sobject
• sf schema generate tab
• sf lightning generate app
• sf lightning generate component
• sf lightning generate test <---------- WHAT IS THIS ??

[tmkw]

need to add required ruby version to gemspec

[tmkw]

After some consideration, those must be added for my use: [gemspec]

• homepage issue
• ruby version must be specified

[sf command] sf commands are so many. So, I will divide them into some releases:

(0.0.3)

• sf project deploy start
• sf project retrieve start
• sf org list
• sf org logout
• sf org display user
• sf alias list

(0.0.4)

• sf apex generate class
• sf apex generate trigger
• sf apex get test
• sf apex run
• sf apex run test

(0.0.5)

• sf schema generate field
• sf schema generate sobject
• sf schema generate tab

(0.0.6)

• sf lightning generate app
• sf lightning generate component
• sf lightning generate test

(0.0.7)

• sf data create record
• sf data delete record
• sf data get record
• sf data update record

(0.0.8) sf data bulk operations?

[tmkw]

with 0.0.3, I want to change some desgin with this change, I will do like this:

  sf = SfCli::Sf.new

  sf.target_org = :hoge

  sf.org.display   #=> returns org 'hoge''s information
  sf.org.display :bar #=> returns org 'bar''s information

  sf.data.query 'SOQL'
  sf.data query 'SOQL', target_org: :bar

[tmkw]

hmm, does that make sence?? need more consideration....

[tmkw]

...in 0.0.3:

• rubygem's issues (homepage, ruby version)
• design change (I'll explain later)

design change:

• each operation can have its own target org.

sf = SfCli::sf.new
sf.org.login_web  # login to default org

sf.org.target_org = :hoge
sf.org.login_web  # login to org "hoge"

sf.data.query "SELECT ...."  # query against default org

sf.data.target_org = :bar  # set bar as target org
sf.data.query "SELECT ..."  # query against org 'bar'

hmmm....

[tmkw]

Also, unit testings should be all included as 0.0.3.

adding sf command operations are after 0.0.4.

[tmkw]

CONCLUSION

0.0.3 includes:

1. rubygem's issues (homepage, ruby version)

2. design change:

   • stop keeping target-org as instance variable.
   • keep classes just thin wrapper of sf command as possible
   • keep library as fluent api as possible

sf = SfCli::sf.new
sf.org.login_web  # login to default org
sf.org.login_web target_org: :hoge  # login to org "hoge"

sf.data.query "SELECT ...."  # query against default org
sf.data.query "SELECT ..." , target_org: :bar  # query against org 'bar'

you must specify target_org every time when you access any orgs except default one.

3. all tests should be set up and implemented

   • cucumber
   • rspec

4. refactoring

   • exception class for each operation
   • use json responses
   • command line construction
   • debug mode

5. operations add:

   • sf project deploy start
   • sf project retrieve start
   • sf org list
   • sf org logout
   • sf org display user
   • sf alias list

[tmkw]

with 0.0.1/refactoring, from 1 to 3 and most of 4 has been done.

so, tasks left for 0.0.3....

4. refactoring exception class for each operation

operations add:

• sf project deploy start
• sf project retrieve start
• sf org list
• sf org logout
• sf org display user
• sf alias list

[tmkw]

I think the contents of 0.0.7 draft should be included in 0.0.3

(0.0.7)

sf data create record sf data delete record sf data get record sf data update record

[tmkw]

from priority perspective, the following should be included. it's ok that other candidates go to 0.0.7

• exception class for each operation
• sf data create record
• sf data delete record
• sf data get record
• sf data update record
• sf project deploy start
• sf project retrieve start

[tmkw]

go to 0.0.7

• sf org list
• sf org logout
• sf org display user
• sf alias list

[tmkw]

About 0.0.4 later, the followings are just idea.

0.0.4

• sf data create record
• sf data delete record
• sf data get record
• sf data update record

all done :+1:

0.0.5

bulk operations

0.0.6

• sf project deploy start
• sf project retrieve start

0.0.7

• sf apex generate class
• sf apex generate trigger
• sf apex run
• sf apex run test
• sf apex get test

0.0.8

operations for non scratch org:

• sf org list => 0.0.5
• sf org list auth
• sf org list limits
• sf org list metadata
• sf org list metadata-types

0.0.9

operations for non scratch org:

• sf org logout
• sf org display user
• org login access-token
• sf alias list

0.0.10

sf schema generate sobject sf schema generate field sf schema generate tab

0.0.11

• sf lightning generate app
• sf lightning generate component
• sf lightning generate test
• sf lightning generate event
• sf lightning generate interface

0.0.12

sf api rest operations

0.0.13

sf api other operations OR sf org: scratch-org operations ?