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

Preview v5: Add explanation that individual initialisation will throw errors #352

Merged
merged 1 commit into from
Oct 3, 2023

Conversation

romaricpascal
Copy link
Member

As we decided that to start with, we’d limit our public API to “we throw errors”, we don’t have any specific errors to document as part of our JavaScript API Reference.

I think we don't need more than an update to “Select and initialise individual components” (Netlify preview), which this PR adds.

Only other thing I could think of may be to discuss “Initialising components” to the JavaScript API Reference to explain that initAll doesn’t throw but logs and individual initialisation throws, but there’s a bit of overlap with the JavaScript section of Import CSS, assets and JavaScript that lists all the options for initialising already. Seems like this would be a wider piece of work around structuring how we organise the JavaScript API docs (especially to keep the component names in the menu).

Part of the work for #341

@netlify
Copy link

netlify bot commented Oct 2, 2023

Deploy Preview for govuk-frontend-docs-preview ready!

Name Link
🔨 Latest commit 68fa05d
🔍 Latest deploy log https://app.netlify.com/sites/govuk-frontend-docs-preview/deploys/651ae252000a8c0008f895e7
😎 Deploy Preview https://deploy-preview-352--govuk-frontend-docs-preview.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@romaricpascal romaricpascal force-pushed the document-errors branch 2 times, most recently from 596c0b1 to 8e522c3 Compare October 2, 2023 13:32
@romaricpascal romaricpascal force-pushed the document-errors branch 2 times, most recently from 760452a to 8708ed7 Compare October 2, 2023 13:50
@colinrotherham colinrotherham self-requested a review October 2, 2023 14:50
Copy link
Contributor

@colinrotherham colinrotherham left a comment

Choose a reason for hiding this comment

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

Looks good. Minor formatting comment but not a blocker

Co-authored-by: Colin Rotherham <colin.rotherham@digital.cabinet-office.gov.uk>
@romaricpascal
Copy link
Member Author

@colinrotherham Cheers! Updated.
@claireashworth Does it all look OK from a content perspective as well? 😊

@claireashworth
Copy link
Contributor

Looks good to me

@romaricpascal romaricpascal merged commit caa486c into release/5.0 Oct 3, 2023
5 checks passed
@romaricpascal romaricpascal deleted the document-errors branch October 3, 2023 08:56
@romaricpascal romaricpascal changed the title Add explanation that individual initialisation will throw errors Preview v5: Add explanation that individual initialisation will throw errors Oct 23, 2023
@colinrotherham colinrotherham restored the document-errors branch October 23, 2023 17:31
@colinrotherham colinrotherham deleted the document-errors branch October 23, 2023 17:32
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