Skip to content

Feat 168 feature map featuremap#71

Merged
tshuck-beyond merged 10 commits intofeat-167-add-option-to-use-simplecov-datafrom
feat-168-feature-map-featuremap
Mar 13, 2025
Merged

Feat 168 feature map featuremap#71
tshuck-beyond merged 10 commits intofeat-167-add-option-to-use-simplecov-datafrom
feat-168-feature-map-featuremap

Conversation

@tshuck-beyond
Copy link
Collaborator

Based on work from #68. Adds some basic feature mapping + fictional team ownership to feature map such that it can generate its own data for local development.

@tshuck-beyond tshuck-beyond force-pushed the feat-167-add-option-to-use-simplecov-data branch from a072e8f to 686be3e Compare March 13, 2025 12:47
@tshuck-beyond tshuck-beyond force-pushed the feat-168-feature-map-featuremap branch from 59db050 to af6f414 Compare March 13, 2025 12:49
Copy link
Collaborator

@hstrowd hstrowd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is great. Should we add a step to CI to run bundle exec featuremap validate to demonstrate some of the CI setup we expect/recommend users to employ?

url: https://github.com/Beyond-Finance/feature_map
# Supports link generation in message construction, e.g., release announcements
documentation_site_url: example.github.io/repo
documentation_site_url: https://beyond-finance.github.io/feature_map/
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems a bit dangerous/problematic in this case because the library assumes this is a FeatureMap docs site (source) but in this case that is not the case. This URL is the library user documentation. I would favor using fake URL that more clearly demonstrates the purpose of this URL (e.g. something like https://example.com/feature/map/docs/site/).

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh yup. I confused myself here -- great call.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you think that it would be weird to link here? https://beyond-finance.github.io/feature_map/example-docs-site.html

@tshuck-beyond tshuck-beyond force-pushed the feat-168-feature-map-featuremap branch from a4ef711 to 00e0933 Compare March 13, 2025 13:24
@tshuck-beyond tshuck-beyond force-pushed the feat-168-feature-map-featuremap branch from 5a1e9c3 to c2f0eb6 Compare March 13, 2025 13:26
@tshuck-beyond tshuck-beyond merged commit 859ea8c into feat-167-add-option-to-use-simplecov-data Mar 13, 2025
8 checks passed
@tshuck-beyond tshuck-beyond deleted the feat-168-feature-map-featuremap branch March 13, 2025 14:30
tshuck-beyond added a commit that referenced this pull request Mar 13, 2025
* Allow test coverage data to be derived from simplecov reports

* Use simplecov and POC feature mapping within library to demonstrate simplecov test coverage

* Add notes about simplecov commands to test coverage usage

* Add updated docs based on updated config

* Feat 168 feature map featuremap (#71)

* Use slightly more realistic teams

* Add basic feature definitions

* Apply initial assignments

* Update feature map spec to account for new feature mapping

* Use real test coverage data for local development

* Remove unused sample config

* Update references to sample config

* Commit sample data to make CI a bit easier

* Add feature map assignment validation

* Clarify docs site link in config
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants