Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement property resolver strategy #109

Open
longwa opened this issue May 8, 2018 · 0 comments
Open

Implement property resolver strategy #109

longwa opened this issue May 8, 2018 · 0 comments
Assignees
Milestone

Comments

@longwa
Copy link
Owner

longwa commented May 8, 2018

Current default properties are either generated based on handler rules or supplied by TestDataConfig.

As part of the refactor for 3.3, the groundwork is in place to allow for pluggable property resolvers to allow for more flexibility.

TestDataConfig would just be one of several property resolvers.

Another resolver could use the Faker library to generate more realistic fake data.

One design goal would be to instantiate a single resolver context so that resolvers could carry state to more efficiently create sequential data, unique data, etc.

@longwa longwa self-assigned this Jun 5, 2018
@longwa longwa modified the milestones: 3.0.0, 3.3.2 Jun 5, 2018
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

No branches or pull requests

1 participant