Eric Greer

> There is a bug/unlisted deprecation in Rails 7 regarding .select and how it creates attribute reflections for fields. To fix Add a `has_attribute?` check to anything acting on `after_initialize`...

Either document how to add a trace id (like request id) or generate one so that we can track allow through revoke.

Instead of using a raw stack with simple push and pops we should assign each entry a GUID so that we can have more controlled revoke behavior for easier mixing...

As part of the test cleanup we added rubocop and created exceptions in https://github.com/apsislabs/phi_attrs/blob/master/.rubocop.yml to not impact existing behavior. In the PR for this each of the `# TODO: RUBOCOP`...

Currently the master branch in this repository references version `0.0.8` https://github.com/valiot/administrate-field-enum/blob/e77b4b632ece300666e8492f5707dd30d2c8b571/administrate-field-enum.gemspec#L5 instead of the deployed version 0.0.9 https://rubygems.org/gems/administrate-field-enum/versions/0.0.9 The latest version on ruby gems also doesn't appear to include this...

- Model has phi attributes - Validates length on the attribute in the model - FactoryBot sets the attribute in the factory - Creating with factory gives the phi access...

Fixes #72 Adds uuid for tracking the `allow` to the `disallow` so that you can trace the access better. Full Stack may look similar to: ``` 2025-02-12T16:48:57.288185 INFO: [PHI Access...

Log files that get very long or have multiple allow grants it can be tough to identify the access grant enabled with the corresponding disable. ```sh 2024-10-10T03:41:17.094931 INFO: [PHI Access...

There is a possibility that if the active record is forked in the middle of initialization when under periods of high load that we define a wrapped method twice where...