We already have set our API version to 3, and have got an update function.

However, further changes may be in the pipeline.

While we're still in alpha, and we just add more functionality to our update, we may make more changes after a stable release, and it would be useful to be able to have API 3.1, say.

Also, this cleans up the slightly messy naming of the update classes.

CommentFileSizeAuthor
#1 1877448.flag_.update-handler-classes-names.patch3.29 KBjoachim

Comments

joachim’s picture

joachim commented
Status: Active » Fixed
StatusFileSize
new 1877448.flag_.update-handler-classes-names.patch3.29 KB

Issue #1877448 by joachim: Changed update system to have clearer class names and allow API point versions.

This means a future update to 3.1 would need:

/**
 * Flag update class for API 3.1 flags.
 */
class FlagUpdate_3_1 {

  public $old_api_version = 3.0;
  public $new_api_version = 3.1;

  static function update(&$flag) {
  }
}

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

Anonymous’s picture

(not verified) commented
Issue summary: View changes

example