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

Ensure parameter names match ColdFusion 2018+ #898

Open
KamasamaK opened this Issue Aug 10, 2018 · 1 comment

Comments

Projects
None yet
2 participants
@KamasamaK
Contributor

KamasamaK commented Aug 10, 2018

This refers to the parameter names used in NamedParametersColdFusion2018.pdf

I think these are mostly good, but this issue will be a reminder for me (or anyone else) to go through all of them to ensure that they match. Lucee already supported this feature, and they have already ensured via LDEV-1806 that they at least have aliases for the ColdFusion names. Because of this, we should go with the more restrictive name.

@KamasamaK

This comment has been minimized.

Show comment
Hide comment
@KamasamaK

KamasamaK Aug 14, 2018

Contributor

I've started this and I've found there to be more discrepancies than I expected. Also, there are discrepancies between the PDF and the web docs, so I'm siding with the PDF for now until I can get confirmation. Also, multiple signatures (#529) is complicating it, so for now I'm keeping with combining the params e.g. value or callback.

Contributor

KamasamaK commented Aug 14, 2018

I've started this and I've found there to be more discrepancies than I expected. Also, there are discrepancies between the PDF and the web docs, so I'm siding with the PDF for now until I can get confirmation. Also, multiple signatures (#529) is complicating it, so for now I'm keeping with combining the params e.g. value or callback.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment