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

Include sanitised supplier name in agreement document filename #203

Merged
merged 3 commits into from
Nov 3, 2015

Conversation

TheDoubleK
Copy link
Contributor

CCS use supplier name to organise their work, so they need it to be included in the filename for the returned agreement documents.

This is exactly the same method used in the script to generate the framework agreement data.

I have confirmed with Chris at CCS that the filename format generated here is good for them to work with.

)


def _sanitise_supplier_name(supplier_name):
Copy link
Contributor

Choose a reason for hiding this comment

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

I feel like this shouldn't be private, it's useful in it's own right at least in scripts.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yep, fair point. Sorted.

CCS use supplier name to organise their work, so they need it to be included in the filename for the returned agreement documents.
@TheDoubleK TheDoubleK force-pushed the sanitise-supplier-names branch from 76110e0 to 0cfb83d Compare November 3, 2015 09:45
@TheDoubleK TheDoubleK force-pushed the sanitise-supplier-names branch from 7e696f1 to 720b1ab Compare November 3, 2015 09:56
@robyoung
Copy link
Contributor

robyoung commented Nov 3, 2015

👍

TheDoubleK added a commit that referenced this pull request Nov 3, 2015
Include sanitised supplier name in agreement document filename
@TheDoubleK TheDoubleK merged commit a84cd4e into master Nov 3, 2015
@quis quis deleted the sanitise-supplier-names branch November 9, 2015 20:39
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