Summary: 102 instances, 91 unique

Text	Count
data: undefined, // TODO allow plugins to provide context data	1
// TODO this may require a little breaking change for ideal-image users?	1
// TODO this triggers whole sidebar re-renders on navigation	1
// TODO not ideal, see also "useDocs"	1
// TODO do we have other use-cases than image assets?	1
// TODO handle context for nested routes	1
// TODO should we allow "items" here? how would this work? would an	1
// TODO repeatedly process & unwrap autogenerated items until there are no	1
// TODO: it should be removed from here	1
// TODO stop hardcoding items?	2
// TODO improve	1
// TODO handle properly all the navbar item types here!	1
// TODO improve types, use unions	1
// TODO this feature should be provided by docusaurus core	1
// TODO deduplicate: also present in @docusaurus/utils	1
// TODO: Joi doesn't allow mutual recursion. See https://github.com/sideway/joi/issues/2611	1
// TODO this would be better to do all that in the codegen phase	1
// TODO integrate this as part of the script	1
// TODO: Find a better way to do so, possibly by compiling the Markdown content,	1
// TODO temporary casting until ThemeConfig type is improved	2
// TODO legacy, the sidebar name is like "version-2.0.0-alpha.66/docs"	1
// TODO add other stable classNames here	3
// TODO require theme exhaustive config, fail fast?	1
// TODO temporary, the current order is bad and we should change/fix that	1
// TODO implementation can be completed/enhanced	1
// TODO avoid conflicts with the ideal-image plugin	1
// TODO legacy retro-compatibility due to old versioned sidebars using	2
// TODO support md/mdx too? (may be overkill)	1
// TODO we should complete this theme config type over time	1
// TODO temporary (@alpha-58)	1
// TODO this is not ideal to have to maintain such a list of allowed chars	1
// TODO temporary (@alpha-58)	2
// TODO replace by starter repo in Docusaurus-community org (if we get it)	1
// TODO maybe move these 2 themeConfig to siteConfig?	1
// TODO move to SiteMetadataDefaults or theme-common ?	2
// TODO how can the order be defined for mobile?	1
// TODO `require` this?	1
// TODO recover from short theme-names here: "classic" => "@docusaurus/theme-classic"	1
// TODO maybe make ensure the permalink is valid url path?	1
wrap: 'forbidden', /// TODO allow wrapping objects???	1
// TODO deduplicate: also present in @docusaurus/utils-common	1
// TODO make this version-aware; maybe we need a	1
// TODO should probably not even appear here	1
// TODO instead of default browser install UI, show custom docusaurus	1
// TODO change to export default after migrating to ESM	1
// TODO is versioning the id very useful in practice?	1
// TODO temp workaround: non-comps should be forbidden to wrap	1
// TODO `require` this?	1
// TODO these events still works in chrome but have been removed from the spec	1
// TODO remove when migrating to ESM	1
//  TODO handle properly all the navbar item types here!	1
// TODO after we have forked prism-react-renderer, we should tweak the	1
// TODO how to describe this one properly?	1
// TODO: it's not really clear what should be the behavior if 2 tags have	1
// TODO remove this check once fixed in Yarn PnP	1
// TODO this event still works in chrome but has been removed from the spec	1
// TODO for retrocompatibility with existing behavior	1
// TODO support correct alternate url when localized site is deployed on	1
// TODO enable deprecation warnings later	1
// TODO move to design system folder	2
// TODO create dedicated testing utility for mocking contexts	1
// TODO how can we make this emit a custom error message :'(	1
// TODO: remove once with proper Joi support	1
// TODO legacy retrocompatibility	2
/* TODO: deprecation, need to remove this after Safari will support `::marker` */	1
// TODO read routes and automatically detect internal/external links?	1
// TODO tags should be a sub route of the version route	1
// TODO proper detection is currently unreliable!	1
// TODO tags should be a sub route of the version route	2
// TODO move to @docusaurus/utils-validation	2
{/* TODO double check those article meta array syntaxes, see https://ogp.me/#array */}	1
// TODO deprecate getSwizzleComponentList later	1
// TODO: import from theme-common once we only support Node.js with ESM support	1
// TODO deep merge this	1
// TODO legacy APIs kept for retro-compatibility: deprecate them	1
// TODO all this seems hacky	1
// TODO this item should probably not receive the "activePath" props	1
TODO we should probably add a real e2e test in core instead of using our own	1
// TODO: the whole code is designed for pipeline operator	1
// TODO temporary types	1
// TODO legacy id retro-compatibility!	1
// TODO make the hardcoded theme-classic classnames configurable (or add them	1
// TODO can probably be refactored	1
// TODO alpha-60: remove this deprecated lifecycle soon	1
// TODO: try to use path.relative()	1
// TODO provide util so that theme authors can also check exhaustiveness?	1
// TODO provide additional md processing here? like interlinking pages?	1
// TODO all this wouldn't be necessary if we used ReactRouter basename feature	1
// TODO use "projects" + multiple configs if we work on another theme?	1
// TODO we should use ReactRouter basename feature instead!	1
// TODO infer this from reading the image	1