8

The question API Tags got me thinking. What is the organisation of *apex-** tags going to look like. Not surprisingly the apex tag already exists, but what about more specific tags, here are some suggestions I can think of:

  • apex-rest: for @RestResource classes
  • apex-batch
  • apex-schedulable

I am sure there are heaps more.

16

I don't think creating merged tags like this will add any value. Instead it will be better if we add 2 separate tags. So instead of apex-rest, use apex and rest.

This will also help members who like to subscribe to individual tags, and also avoid creating new tags (with weird annotations like apex-workflow) when 2 separate tags can do the job. That's my 2 cents anyway.

Anup

  • Agreed. I think we want to avoid creating hierarchies and complicated taxonomies since tags were created specifically to avoid that. – Greg Grinberg Aug 2 '12 at 17:06
  • Thanks for the feedback, I agree with you both on the matter. – Daniel Blackhall Aug 3 '12 at 21:40
  • Agree with this 100%. batch would be another prime candidate as any apex developer will know what it consists of. – Matt Lacey Aug 7 '12 at 3:53
  • 1
    Agreed, and let me put it another way: As a member of the apex code dev team, I keep a browser tab open to salesforce.stackexchange.com/questions/tagged/… <-- very convenient ;) – Rich Unger Aug 29 '12 at 18:45

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .