-
Notifications
You must be signed in to change notification settings - Fork 1k
Added retirement warning on Field customizers #10308
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
Conversation
I'm not sure on the wording, but there SHOULD be a warning on the page ensuring that people are aware of the upcoming retirement
Learn Build status updates of commit 955c247:
|
File | Status | Preview URL | Details |
---|---|---|---|
docs/spfx/extensions/get-started/building-simple-field-customizer.md | View | Details |
docs/spfx/extensions/get-started/building-simple-field-customizer.md
- Line 12, Column 1: [Warning: h1-not-first - See documentation]
Markdown content is not allowed before H1 'Build your first Field Customizer extension'.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
Learn Build status updates of commit 3c65d4b:
|
File | Status | Preview URL | Details |
---|---|---|---|
docs/spfx/extensions/get-started/building-simple-field-customizer.md | View | Details |
docs/spfx/extensions/get-started/building-simple-field-customizer.md
- Line 12, Column 1: [Warning: h1-not-first - See documentation]
Markdown content is not allowed before H1 'Build your first Field Customizer extension'.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
I'm well aware my wording probably isn't the right here, but there ABSOLUTLY needs to be a statement on the page about the planned retirement - the sooner the better. |
Learn Build status updates of commit 7292e67:
|
File | Status | Preview URL | Details |
---|---|---|---|
docs/spfx/extensions/get-started/building-simple-field-customizer.md | View | Details |
docs/spfx/extensions/get-started/building-simple-field-customizer.md
- Line 12, Column 1: [Warning: h1-not-first - See documentation]
Markdown content is not allowed before H1 'Build your first Field Customizer extension'.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
Learn Build status updates of commit d16b92b:
|
File | Status | Preview URL | Details |
---|---|---|---|
docs/spfx/extensions/get-started/building-simple-field-customizer.md | View | Details |
docs/spfx/extensions/get-started/building-simple-field-customizer.md
- Line 12, Column 1: [Warning: h1-not-first - See documentation]
Markdown content is not allowed before H1 'Build your first Field Customizer extension'.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
Learn Build status updates of commit 9c1982a: ✅ Validation status: passed
For more details, please refer to the build report. |
I'm not sure on the wording, but there SHOULD be a warning on the page ensuring that people are aware of the upcoming retirement
Category
Related issues
N/A
What's in this Pull Request?
A retirement warning for SPFx field customizers