`@since {version}` for released, `@since TBD` for unreleased (5 in the tree today). `gktools replace-since` rewrites TBD at release. The changelog in `readme.txt` uses a `= TBD =` heading for the same reason. **Do not hand-replace it with a version.**
### Code Style
No `.phpcs.xml` in the repo. Follow WordPress spacing as written in the existing files. Two rules this codebase actively enforces via tests:
– `rgar( $array, $key )` over `$array[‘key’]` for entry and choice access.
– Strict comparison: `in_array( …, true )`, `===` over `==` for string literals.
## Extension Patterns
### Adding a new field type
1. Create `includes/fields/class-gravityview-inline-edit-field-{type}.php`. The glob picks it up; no registration list to edit.
2. Extend `GravityView_Inline_Edit_Field`, set `$gv_field_name` (the GF field type) and `$inline_edit_type` (the x-editable type).
3. Override `modify_inline_edit_attributes()` to add `data-*` the JS needs. **Call `parent::` at the end**: the base adds `data-type` and optionally `data-value`.
4. Override `updated_result()` to shape the live-update payload.