[padding-line-between-statements] Add an option for padding object elements

What rule do you want to change?

padding-line-between-statements

Does this change cause the rule to produce more or fewer warnings?

More warnings, if enabled. (but none if --fix is enabled.)

How will the change be implemented? (New option, new default behavior, etc.)?

New option for STATEMENT_TYPE for object elements.

Please provide some example code that this change will affect:

const obj = {
  props: {
    elt: Object,
  },
  data() {
    return {
      selected: {},
      config: {
        card_mode: false
      },
    };
  },
  created() {
    this.today = new Date;
  },
  methods: {
    onSubmit() {
      const url = '/foo';
      this.POST(url, {
        selected: this.selected,
      });
    },
    onReset() {
      this.$nextTick(() => this.$bvModal.hide('modal'));
    },
  },
};

What does the rule currently do for this code?

Nothing

What will the rule do after it’s changed?

Add padding between object elements this:

const obj = {
  props: {
    elt: Object,
  },

  data() {
    return {
      selected: {}

      config: {
        card_mode: false
      },
    };
  },

  created() {
    this.today = new Date;
  },

  methods: {
    onSubmit() {
      const url = '/foo';
      this.POST(url, {
        selected: this.selected,
      });
    },

    onReset() {
      this.$nextTick(() => this.$bvModal.hide('modal'));
    },
  },
};

Are you willing to submit a pull request to implement this change?

Nooooo.

[jiangfengming]

+1. Before ESLint officially support it, I modified the lines-between-class-members rule and made lines-between-object-properties.

[mdjermanovic]

Hi @mat813, thanks for this proposal!

padding-line-between-statements is about statements, so it probably shouldn’t apply to elements in object literals.

Some of the alternatives might be:

• New rule for object literals only, similar to how we already have lines-between-class-members for classes.
• New rule which would replace existing padding rules, as proposed in this comment by @kaicataldo.
• New option (or options) in object-property-newline.

I’m not sure which of these would be the best choice at the moment.