Skip to content

Document identifier normalizers #457

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

Merged
merged 1 commit into from
Apr 6, 2018

Conversation

soyuka
Copy link
Member

@soyuka soyuka commented Apr 6, 2018

No description provided.

# Identifiers

Every item operation has an identifier in it's URL. Although this identifier is usually a number, it can also be an `UUID`, a date, or the type of your choice.
To help with your developer experience, we introduced an identifier normalization process.
Copy link
Contributor

Choose a reason for hiding this comment

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

developer -> development ?

@soyuka soyuka force-pushed the identifier-normalizer branch from d607e6a to 4571ffb Compare April 6, 2018 13:15
@Simperfit Simperfit merged commit 10fcd7b into api-platform:master Apr 6, 2018
@Simperfit
Copy link
Contributor

Thanks @soyuka!

public function getItem(string $resourceClass, $identifiers, string $operationName = null, array $context = [])
{
// Our identifier is:
// $id['code']
Copy link
Contributor

Choose a reason for hiding this comment

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

$identifiers instead of $id ?
Here and bellow...

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes ! This is why I wanted some reviews before @Simperfit merged :p now he will fix it because he said he took full responsability :D

Copy link
Contributor

Choose a reason for hiding this comment

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

hehe, going to do it.

@soyuka soyuka deleted the identifier-normalizer branch April 9, 2018 14:56
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.

3 participants