DEVELOPMENT.md

Release Guide

htmlburger/carbon-fields

1. Merge all changes for the new version into master
2. Bump version numbers in config.php and package.json according to SemVer
3. Commit bumped version changes to master
4. Checkout release
5. Merge master into release. NEVER merge release into any other branch - only merge branches INTO release.
6. Run npm install && npm run build
7. You should now have changes ONLY in the /assets/dist/ directory - any changes outside this directory mean that you have a dirty working copy. Never commit anything else into release except /assets/dist/ changes.
8. Commit the /assets/dist/ changes to release
9. git push --all
10. Create a new release in Github from the release branch
11. Enter the new version you set in config.php for Tag version and Title
12. Add a changelog for Description
13. Click Publish release

htmlburger/carbon-fields-plugin

1. Update the version in carbon-fields-plugin.php, readme.txt and composer.json for htmlburger/carbon-fields to match the newly released version
2. Commit to master
3. Create a new release in Github from the master branch
4. Enter the new version for Tag version and Title (you can skip the changelog)
5. Click Publish release

Internal Glossary

value_set

Represents a single field value. Complex_Field uses a value_tree instead which contains a value_set for every child field including the Complex_Field itself.

Note: The Value_Set class will always return a fully formatted value_set with all of its properties OR null

Schema

array(
	array(
		'value' => <mixed>,
		property<string> => <mixed>,
		...
	),
	...
)