Reworked custom measurements

.gitattributes

@@ -0,0 +1,2 @@
+/tests/generated/** linguist-generated=true
+/benches/generated/** linguist-generated=true

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,39 @@
+---
+name: Bug Report
+about: Report a bug to help us improve!
+title: ''
+labels: bug
+assignees: ''
+---
+
+## `taffy` version
+
+The release number or commit hash of the version you're using.
+
+## Platform
+
+What platform are you using `taffy` on? e.g. Rust, Android, IOS, JavaScript/TypeScript
+
+## What you did
+
+The steps you took to uncover this bug.
+
+Please provide a runnable code snippet or link to an example that demonstrates the problem if you can.
+
+## What went wrong
+
+If it's not clear:
+
+- what were you expecting?
+- what actually happened?
+
+## Additional information
+
+Other information that can be used to further reproduce or isolate the problem.
+This commonly includes:
+
+- screenshots
+- logs
+- theories about what might be going wrong
+- workarounds that you used
+- links to related bugs, PRs or discussions

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,24 @@
+---
+name: Feature Request
+about: Propose a new feature!
+title: ''
+labels: enhancement
+assignees: ''
+---
+
+## What problem does this solve or what need does it fill?
+
+A description of why this particular feature should be added.
+
+## What solution would you like?
+
+The solution you propose for the problem presented.
+
+## What alternative(s) have you considered?
+
+Other solutions to solve and/or work around the problem presented.
+
+## Additional context
+
+Any other information you would like to add such as related previous work,
+screenshots, benchmarks, etc.

.github/dependabot.yml

@@ -0,0 +1,14 @@
+version: 2
+updates:
+ - package-ecosystem: cargo
+ directory: /
+ schedule:
+ interval: weekly
+ labels:
+ - "dependencies"
+ - package-ecosystem: github-actions
+ directory: /
+ schedule:
+ interval: weekly
+ labels:
+ - "dependencies"

.github/linters/.markdown-lint.yml

@@ -0,0 +1,29 @@
+---
+###########################
+###########################
+## Markdown Linter rules ##
+###########################
+###########################
+
+# Linter rules doc:
+# - https://github.com/DavidAnson/markdownlint
+#
+# Note:
+# To comment out a single error:
+# <!-- markdownlint-disable -->
+# any violations you want
+# <!-- markdownlint-restore -->
+#
+
+###############
+# Rules by id #
+###############
+# MD013:
+# line_length: 120
+
+#################
+# Rules by tags #
+#################
+# blank_lines: false # Error on blank lines
+line_length: false # Ignore excessively long lines
+no-duplicate-heading: false # This is useful in RELEASES.md

.github/pull_request_template.md

@@ -0,0 +1,21 @@
+# Objective
+
+Why did you make this PR?
+
+If you're fixing a specific issue, say "Fixes #X" and the linked issue will be automatically closed when this PR is merged.
+If it's not obvious, describe how this changes made addressed the objectives.
+
+**Changes that will affect external library users must update RELEASES.md before they will be merged.**
+
+## Context
+
+Discuss any context that may be needed for reviewers to understand the changes you've made.
+This may include related issues, previous discussion, or links to documentation or code.
+
+## Feedback wanted
+
+> This section is optional. If there are no particularly tricky or controversial changes, you can delete this section.
+
+Which parts of this PR were you unsure about? Which parts were particularly tricky?
+
+If you're stuck on part of the changes or want feedback early, open a draft PR and list the items that need to be completed here using a [checklist](https://github.blog/2014-04-28-task-lists-in-all-markdown-documents/).

.github/workflows/ci.yml

@@ -0,0 +1,95 @@
+on: [push, pull_request]
+
+name: Continuous integration
+
+jobs:
+ test-features-none:
+ name: "Test Suite [Features: None]"
+ runs-on: ubuntu-latest
+ steps:
+ - uses: actions/checkout@v3
+ - uses: actions-rs/toolchain@v1
+ with:
+ profile: minimal
+ toolchain: stable
+ override: true
+ - uses: actions-rs/cargo@v1
+ with:
+ command: test
+ args: --no-default-features
+
+ test-features-default:
+ name: "Test Suite [Features: Default]"
+ runs-on: ubuntu-latest
+ steps:
+ - uses: actions/checkout@v3
+ - uses: actions-rs/toolchain@v1
+ with:
+ profile: minimal
+ toolchain: stable
+ override: true
+ - uses: actions-rs/cargo@v1
+ with:
+ command: test
+
+ test-features-alloc:
+ name: "Test Suite [Features: alloc]"
+ runs-on: ubuntu-latest
+ steps:
+ - uses: actions/checkout@v3
+ - uses: actions-rs/toolchain@v1
+ with:
+ profile: minimal
+ toolchain: stable
+ override: true
+ - uses: actions-rs/cargo@v1
+ with:
+ command: test
+ args: --no-default-features --features alloc
+
+ fmt:
+ name: Rustfmt
+ runs-on: ubuntu-latest
+ steps:
+ - uses: actions/checkout@v3
+ - uses: actions-rs/toolchain@v1
+ with:
+ profile: minimal
+ toolchain: stable
+ override: true
+ - run: rustup component add rustfmt
+ - uses: actions-rs/cargo@v1
+ with:
+ command: fmt
+ args: --all -- --check
+
+ clippy:
+ name: Clippy
+ runs-on: ubuntu-latest
+ steps:
+ - uses: actions/checkout@v3
+ - uses: actions-rs/toolchain@v1
+ with:
+ profile: minimal
+ toolchain: nightly
+ override: true
+ - run: rustup component add clippy
+ - uses: actions-rs/cargo@v1
+ with:
+ command: clippy
+ args: -- -D warnings
+
+ markdownlint:
+ name: Markdown Lint
+ runs-on: ubuntu-latest
+ steps:
+ - uses: actions/checkout@v3
+ with:
+ # Full git history is needed to get a proper list of changed files within `super-linter`
+ fetch-depth: 0
+ - name: Run Markdown Lint
+ uses: docker://ghcr.io/github/super-linter:slim-v4
+ env:
+ VALIDATE_ALL_CODEBASE: true
+ VALIDATE_MARKDOWN: true
+ DEFAULT_BRANCH: master

.github/workflows/dependencies.yml

@@ -0,0 +1,71 @@
+name: Dependencies
+
+on:
+ pull_request:
+ paths:
+ - '**/Cargo.toml'
+ - 'deny.toml'
+ push:
+ paths:
+ - '**/Cargo.toml'
+ - 'deny.toml'
+ branches-ignore:
+ - 'dependabot/**'
+ # schedule:
+ # - cron: "0 0 * * 0"
+
+env:
+ CARGO_TERM_COLOR: always
+
+jobs:
+ check-advisories:
+ runs-on: ubuntu-latest
+ steps:
+ - uses: actions/checkout@v3
+ - uses: actions-rs/toolchain@v1
+ with:
+ toolchain: stable
+ override: true
+ - name: Install cargo-deny
+ run: cargo install cargo-deny
+ - name: Check for security advisories and unmaintained crates
+ run: cargo deny check advisories
+
+ check-bans:
+ runs-on: ubuntu-latest
+ steps:
+ - uses: actions/checkout@v3
+ - uses: actions-rs/toolchain@v1
+ with:
+ toolchain: stable
+ override: true
+ - name: Install cargo-deny
+ run: cargo install cargo-deny
+ - name: Check for banned and duplicated dependencies
+ run: cargo deny check bans
+
+ check-licenses:
+ runs-on: ubuntu-latest
+ steps:
+ - uses: actions/checkout@v3
+ - uses: actions-rs/toolchain@v1
+ with:
+ toolchain: stable
+ override: true
+ - name: Install cargo-deny
+ run: cargo install cargo-deny
+ - name: Check for unauthorized licenses
+ run: cargo deny check licenses
+
+ check-sources:
+ runs-on: ubuntu-latest
+ steps:
+ - uses: actions/checkout@v3
+ - uses: actions-rs/toolchain@v1
+ with:
+ toolchain: stable
+ override: true
+ - name: Install cargo-deny
+ run: cargo install cargo-deny
+ - name: Checked for unauthorized crate sources
+ run: cargo deny check sources

.gitignore

@@ -1,3 +1,8 @@
 /target
+/scripts/gentest/target
+
 **/*.rs.bk
 Cargo.lock
+.DS_Store
+
+.vscode

CONTRIBUTING.md

@@ -0,0 +1,82 @@
+# Contributing
+
+This is a cross-team project, aiming to build solid foundations for Rust UI libraries of all sorts.
+New contributions are extremely welcome!
+
+The basic process is simple:
+
+1. Pick an [issue](https://github.com/DioxusLabs/taffy/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22), or [file a new one](https://github.com/DioxusLabs/taffy/issues/new).
+2. Comment in the issue that you plan to tackle it, and the team will assign the task to you.
+3. Submit a PR.
+4. Respond to feedback from reviewers and make sure CI passes.
+
+The PR review process is completely open: help us by commenting on, testing and approving PRs.
+
+If you'd like to help on a consistent basis or are interested in project management, create a Discussions post, and we'll be happy to hand out triage rights.
+
+## Testing
+
+### Running tests
+
+Flexbox layouts are tested by validating that layouts written in this crate perform the same as in Chrome.
+This is done by rendering an equivalent layout in HTML and then generating a Rust test case which asserts that the resulting layout is the same when run through our layout engine.
+
+You can run these tests without setting up a webdriver environment but if you are looking to add any test case you will need to install [chromedriver](http://chromedriver.chromium.org) and [Chrome](https://www.google.com/chrome/).
+If you are developing on macOS this is easy to do through brew.
+
+```bash
+brew install chromedriver
+```
+
+Once you have chromedriver installed and available in `PATH` you can re-generate all tests by running `cargo run --package gentest`. You should not manually update the tests in `tests/generated`. Instead, fix the script in `scripts/gentest/` and re-generate them. This can happen after a refactor. It can be helpful to commit the updated tests in a dedicated commit so that they can be easier to ignore during review.
+
+To add a new test case add another HTML file to `/test_fixtures` following the current tests as a template for new tests.
+
+### Writing tests
+
+1. All tests should be wrapped in a module called `tests` gated by the standard `test` feature flag, to ensure they are not compiled unless tests are being run.
+
+ ```rs
+ #[cfg(test)]
+ mod tests {
+ // Place tests here
+ }
+ ```
+
+2. For unit-testing this should be placed in the same file as the code they are testing
+ 1. If files become extremely long (more than a couple thousand lines of code), tests should be split out into its own file under the same module
+
+ ```rs
+ // file: ./src/my_struct.rs
+ struct MyStruct;
+
+ impl MyStruct {
+ fn some_method() { .. }
+ }
+
+ #[cfg(test)]
+ mod tests {
+ #[test]
+ fn test_of_some_method() { .. }
+ }
+ ```
+
+3. For integration tests this should be placed within the `./tests` folder
+
+ ```rs
+ // file: ./tests/my_integration_test.rs
+ #[test]
+ fn integration_test_one() { .. }
+ #[test]
+ fn integration_test_two() { .. }
+ ```
+
+4. Each test should have a clear intent
+ 1. It should be evident what is being tested (naming, code, comments)
+ 2. When this test fails, it should be easy to understand what went wrong
+ 3. Fixture-based tests (`#[rstest]`) can help improve clarity when many related scenarios need to be checked
+
+## Benchmarking
+
+Benchmarks build on the same infrastructure as testing, and actually benchmarks are automatically generated from test fixtures just like tests.
+Run `cargo bench` to run benchmarks locally.