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

add get FormatError method & fix test #236

Closed
wants to merge 4 commits into from

Conversation

dwibudut
Copy link
Contributor

@dwibudut dwibudut commented Oct 17, 2023

fix error on andig#1

@dwibudut dwibudut changed the title Fix/endpoint format add get FormatError method & fix test Oct 17, 2023
@andig
Copy link
Contributor

andig commented Oct 17, 2023

Shouldnt this target pr branch? Or is this a different approach?

@andig
Copy link
Contributor

andig commented Oct 17, 2023

Thank you for the fix. It feels wrong to add public Api for this purpose though?

@dwibudut
Copy link
Contributor Author

dwibudut commented Oct 18, 2023

Shouldnt this target pr branch? Or is this a different approach?

Hello, I just moved it to the pr target branch and close this pr.
andig#1

@dwibudut
Copy link
Contributor Author

Thank you for the fix. It feels wrong to add public Api for this purpose though?

I think it's the only way to get the FormatError value set on api start.

@dwibudut dwibudut closed this Oct 18, 2023
@andig
Copy link
Contributor

andig commented Oct 18, 2023

@dwibudut though about this some more. Would you be happy with adding

types.Dialect int = iota, V16, V20

add that to the endpoint interface and then a

ocppj.dialectFormatError() ocpp.ErrorCode

That way the interface would at least be less specific?

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