Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Making task names optional #849

Closed
fjtirado opened this issue May 21, 2024 · 1 comment
Closed

Making task names optional #849

fjtirado opened this issue May 21, 2024 · 1 comment
Labels
area: spec Changes in the Specification

Comments

@fjtirado
Copy link
Collaborator

fjtirado commented May 21, 2024

Currently we write

do: 
   tryWith1:
     try: 
         call:
   tryWith2:
      try: 
        call:

execute, try and call are reserved words, tryWith1 is a name the user has to came with

If user is lazy and do not want to invent names (which are useful, as far as I know just for error.instance feature), he might want to write this instead

do:
  - try: 
       name: tryWith1
       call:
  - try: 
      name: tryWith2
      call: 

@fjtirado fjtirado mentioned this issue May 21, 2024
9 tasks
@cdavernas
Copy link
Member

cdavernas commented May 22, 2024

As discussed in PM, this would go against one of the drives of the refactor, which is having proper references, and which you suggested, by the way.

Making names optional would IMO encourage users to malpractice for the sake of lazyness. Malpractice not only because it will make references more technical (using indexes), but also because of maintenance.

Using maps like we are doing now was a brilliant idea of yours, in my opinion:

  • We dont have to enforce some kind of loose name uniqueness control
  • We dont have to enforce naming conventions. Authors write what they want, upper, lower, whichever case as long as its a valid property name
  • It makes references pretty and allows instant identification of a (possibly faulty) component, even for a non-technical person

@cdavernas cdavernas added the area: spec Changes in the Specification label May 22, 2024
@fjtirado fjtirado mentioned this issue Jun 12, 2024
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: spec Changes in the Specification
Projects
Status: Done
Development

No branches or pull requests

2 participants