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

When getting joined attribute, typing errors cause an exception. #3

Open
rogerhillgsy opened this issue Jan 26, 2020 · 0 comments
Open

Comments

@rogerhillgsy
Copy link
Owner

rogerhillgsy commented Jan 26, 2020

Code such as: -

            FluentOpportunity.Opportunity(opportunityId, _service)
                .UseAttribute((string s) => jn.name_long = s, "name")
                .Join<FluentBidManager>( bm => bm.UseAttribute( (int i) => jn.applicant_id = i, "new_staffid"))...

Will throw an unhelpful exception if "new_staffid" is not an integer type. No trace message is issued.
Expected action is that it will issue a trace message and then throw an ArgumentException with a informative error message.

@rogerhillgsy rogerhillgsy changed the title When getting joined attribute, typikng errors cause an exception. When getting joined attribute, typing errors cause an exception. Jan 26, 2020
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